Implementation of the Core J2EE Patterns - Value List Handler .
Most Java 2 Platform, Enterprise Edition (J2EE) applications have a search and query requirement to search and list certain data. In some cases, such a search and query operation could yield results that can be quite large. It is impractical to return the full result set when the client's requirements are to traverse the results, rather than process the complete set. Typically, a client uses the results of a query for read-only purposes, such as displaying the result list. Often, the client views only the first few matching records, and then may discard the remaining records and attempt a new query. The search activity often does not involve an immediate transaction on the matching objects.
In addition to implementing the Core J2EE Pattern, tag libraries have been added to allow for easy intergration into any J2EE web application. The tag libs produce HTML tables from the ValueList, such as the table below:
<entry key="bigRownum"> <bean class="net.mlw.vlh.adapter.jdbc.dynabean.DefaultDynaBeanAdapter"> <!--<property name="dataSource"><ref bean="oracleDataSource"/></property>--> <property name="connectionCreator"> <bean class="net.mlw.vlh.adapter.jdbc.util.StandardConnectionCreator"> <property name="dataSource"><ref bean="oracleDataSource"/></property> <property name="transactionIsolation"><value>8</value></property> </bean> </property> <property name="useName"><value>false</value></property> <property name="showSql"><value>false</value></property> <property name="adapterType"><value>0</value></property> <property name="sql"> <value> SELECT value as "name", sysdate as "tof" FROM big ORDER BY value </value> </property> <property name="sqlPagingSupport"> <bean class="net.mlw.vlh.adapter.jdbc.util.SqlPagingSupport"> <property name="database"><value>oracle</value></property> </bean> </property> </bean> </entry>
A new release 0.1.7 has been made. This release contains:
ValueList is showing up in many blogs... Setting up ValueList with Struts or other frameworks - Kris Thompson
"Some development shops are moving away from a classic business domain model. Frankly, for some applications (like those to baby-sit big relational databases), I'd have to agree with their direction. When you are doing nothing but viewing and entering relational data, a full object-orentied model is overkill." -Better, Faster, Lighter Java
To help me out, let me know how you found ValueList? (SourceForge Forum)
I inherited a J2EE web solution that chose a different component to display tables. Because the other component does all the sorting and paging in the JRE, not the database where it belongs; the solution did not scale at all! I searched the web to find a replacement and was discouraged by the results. So I grabbed code for past projects and started valuelist.sourceforge.net.
Take a look at my desktop application League Master!It is a fantasy football application build with the spring rich client framework. It has an embedded hsql data warehouse that maintains statistical information throughout the year about every player in the nfl and your league. With this information League Master will assist your management of your team from the draft to the final championship game.