How does the Berkeley DB Java API relate to the J2EE standard?
The Berkeley DB Java API does not currently implement any part of the J2EE standard. That said, it does implement the implicit standard for Java Java Collections. The concept of a transaction exists in several Java packages (J2EE, XA, JINI to name a few). Support for these APIs will be added based on demand in future versions of Berkeley DB. • How should I incorporate db.jar and the db native library into a Tomcat or other J2EE application servers? Tomcat and other J2EE application servers have the ability to rebuild and reload code automatically. When using Tomcat this is the case when “reloadable” is set to “true”. If your WAR file includes the db.jar it too will be reloaded each time your code is reloaded. This causes exceptions as the native library can’t be loaded more than once and there is no way to unload native code. The solution is to place the db.jar in $TOMCAT_HOME/common/lib and let Tomcat load that library once at start time rather than putting it into the WAR that gets r
Related Questions
- Why don’t Berkeley DB and Berkeley DB Java Edition both implement a shared set of Java interfaces for the API? Why are these two similar APIs in different Java packages?
- Can I use the Berkeley DB Java API from within a EJB, a Servlet or a JSP page?
- How does the Berkeley DB Java API relate to the J2EE standard?
