ShiftOne Externalized Queries (ExQ)

home \| license \| api docs \| about download
	What is ExQ? Why should I use it? How are query results stored? How does ExQ connect to the database? How do you recommend inserting/updating data? What JSP tags are available for display purposes? How about an example? What is ExQ? ExQ is a system which can help you quickly and cleanly develop a data flow from SQL queries in XML files to ResultSet display with JSP tags. Why should I use it? Reasons to choose ExQ: Clean Architecture for storing SQL Queries outside of Java Code. Queries contain the power of parameter-based logic. Powerful user-independent caching of query results. Extensive set of JSP taglibs that make data display a breeze. Built-in support for paging results. How are query results stored? Data results are held in a generic Cursor interface. Values are accessed throughout using the ResultSet column names. Cursor results never keep the connection to the database open, even when paging. How does ExQ connect to the database? ExQ has a very convenient mechanism where every query references a connector. Initially, a connector is created for each connection location (Driver/DataSource). This also makes switching database information painless. How do you recommend inserting/updating data? ExQ is not built for inserting or updating data. As these functions often require multiple calls, they should be kept in stored procedures. What JSP tags are available for display purposes? Here is some documentation. How about an example? Here is an example application.

ShiftOne ExQ 1.1