This version includes some major extentions like the implementation of the JNDI data source interface. The USQLG now acts as a directory service for data sources. Also added where SQL filter functionality. You can define filters to block SQL statements for each connection by defining regular expressions.
With the new version ships an admin console where you can manage all necessary medatdata like connection urls and permissions, sql filters and JNDI data sources over a web interface.
Theres a problem with the new Rowset Implementation 1.0.1 from Sun that causes the Universal SQL Gateway to crash when used on non US machines. (Where the locale is set other than US). See the problem discussion in this java forum thread |http://forum.java.sun.com/thread.jsp?forum=423&thread=540624&tstart=0&trange=15.
Don't use this Webrowset implementation with the USQLG 0.3. Instead download an older version from http://java.sun.com/developer/earlyAccess/jdbc/jdbc-rowset.html (Size 96KB, Timestamp 08-23-03)
This new version now includes proxy authentication. If your client is behind a HTTP Proxy requiring authentication to access the internet you can indicate a username and password in the connection URL additional to the Proxy IP and Proxy Port.
Over 120 Methods of the JDBC driver have been implemented as well. All methods of DatabaseMetaData and the PreparedStatement classes required for the JDBC 2.0 specification are now fully implemented.
The Universal SQL Gateway development will continue, now supported by the i3g Institute of the University of Applied Sciences in Heilbronn (http://www.i3g.fh-heilbronn.de/). Sun has released a new Rowset Implementation Public Review (java.sun.com/jdbc). We plan to release a new version of the usqlg which supports this official RowSet release till end of October.
The Universal SQL Gateway allows your client application to cummunicate with a database server over JDBC even if a firewall restricts communication to the HTTP protocol.
It is an alternative for rich client GUI applications to communicate with their server database. Instead of additional server side SOAP or RMI calls create your application with performant JDBC calls and use it in your intranet or single pc. This gives you the the benefit of net traffic reduction (no markup), fast calls (you eliminate unnecessary middleware) and no need of dedicatet web servers. Then, If you need to use your distributed application over a firewall simply apply the Universal SQL Gateway.... read more