Displaytag:
Once I used displaytag to process table display, the displaytag interface was very beautiful, but there was a serious deficiency: a large amount of data would seriously damage the system performance. By default, displaytag Retrieves all the data and returns it to the page. For example, if you have 100 data records on five pages, display retrieves 100 records each time, but only displays 20 records, the consequence of doing so is that a large amount of data will slow down the system speed. In particular, if the data source does not use cache to directly connect to the database, each displaytag will re-query all the data in the database, even if you just make a sort. Although later we can use hackCodeThis allows him to only display the data at a time, but this will cause the data export and sorting functions of display to be unable to work normally, which is miserable. At the same time, displaytag is difficult to expand. You only have one way to add the function: hack! Directly punch inSource code! The consequence is that I get a display package of my own, but he can no longer work with the new version of displaytag.
Extremetable
At one time, displaytag was discarded to find ValueList. However, although this ValueList is well designed (it is said that there is also a ValueList mode), it is easy to modify it. However, the interface is ugly, and I do not know much about CSS. I am not interested in finding taglib at the moment. Today, I am hanging out on the Internet. I suddenly saw the "extremtable" mentioned in the white blog. I checked it on the homepage. It's good. This component is much better than ValueList.
- Simple and generous Interface
- Common displaytag functions are supported.
- Allows you to place input components in tables.
- Complete paging mechanism, data can be requested on demand"
- The version is later than 1.0. I am afraid of anything with version less than 1.
I am eager to study it and recommend it to you.