In addition Jencks supports inbound and outbound messaging using APIs like JMS, JAX-RPC, JBI and JCA CCI as well as providing an XA based pooling mechanism for JDBC. e.g. here is how to use Outbound JMS or Outbound JDBC.
Jencks by default reuses the Geronimo JCA connector, WorkManager and TransactionManager - though there are no fixed runtime dependencies on Geronimo so you should be able to use Jencks with JOTM and Jonas too - though we recommend the Geronimo implementations as they are heavily tested and support full XA recovery.
To get an idea for what Jencks can do try looking at the Message Driven POJOs.
RequirementsIf you are already using Spring, to be able to use Jencks you just need the following jars on your classpath
You may need to add some J2EE jars too. You may wish to add a compelete J2EE.jar (such as the geronimo-spec-j2ee.jar). If you are inside Tomcat, it doesn't like j2ee.jar on the classpath, so use the individual jars from Geronimo - e.g. geronimo-spec-j2ee-connector-*.jar for the JCA APIs
If you want to grab a J2EE specification jar we recommend the Apache repository
Adding a JMS provider
To use ActiveMQ you'll need the following jars (more details).
If you are not already using Spring
Then you need to add the following jars
Jencks 1.3 has been released.
This release primary goal is to upgrade to Geronimo 1.1.
For more informations, see the release notes.
We've moved the Jencks source repository over to Subversion now so you can access the repository easily using HTTP or HTTPS for committers. For more details see how to access the Source