Space Index
|
|||||||||||||||||||||||||||||||
0-9 |
APage: ActiveMQMost of the examples and test cases use ActiveMQ's Resource Adaptor already. e.g. see the following examples Message Driven POJOs Outbound JMS
Page: AMQPool
AMQPool Jencks contains an JMS pooled ConnectionFactory specific for ActiveMQ. The main difference with the ActiveMQ provided one is that it plays nicely in a transacted environment (XA or JCA) and can also have better performances in some cases (see this
|
||||||||||||||||||||||||||||||
B |
CPage: CommunityCreated by jstrachan On Wed Jun 07 17:27:36 BST 2006 Using TimTam
Page: Contributing
There are many ways you can help make Jencks a better piece of software - please dive in and help! Try surf the documentation - if somethings confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source cod
|
||||||||||||||||||||||||||||||
DPage: DownloadLatest Releases On this page you can find the binary and source distributions of Jencks. The current release is Jencks 2.0 Release Maven Repositories You can grab a development SNAPSHOT, a release jar or a full binary distribution from the various Maven r
|
E |
||||||||||||||||||||||||||||||
FPage: FAQPage: Features |
GPage: General |
||||||||||||||||||||||||||||||
HHome page: HomeJencks is a lightweight JCA container which is easy to deploy inside Spring to provide Message Driven POJOs. 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
Page: How can I pool MessageListeners
The JCA container will create an instance of your bean and pool them automatically these days, so you don't need to wrap the MessageListener in a pool. The current implementation of Message Driven POJOs will specify a bean reference in the inbound connect
Page: How do I requeue messages
If your MessageListener throws a runtime exception, per the JMS spec: The result of a listener throwing a RuntimeException depends on the sessions acknowledgment mode. AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE - the message will be immediately redelivered.
Page: How do things change if I supply a transaction manager to a connector
If you don't specify a JTA transaction manager on a connector, then Jencks will use local JMS transactions. If you specify a transaction manager it will use XA transactions. The main difference between local and XA is that local is a transaction purely on
Page: How does Jencks compare to Springs MDPs
Spring 2.x has introduced its own Message Driven POJO support. This entry summarises the difference. Jencks supports both inbound and outbound messaging with any API - such as JMS, JDBC and JAX-WS; Spring's MDBs only do inbound messaging on JMS Jencks use
|
I |
||||||||||||||||||||||||||||||
JPage: Jencks 1.0 M1 ReleaseRelease Notes This is the first major milestone of Jencks. We currently have support for working inbound JMS consumption using regular JMS transactions or full XA transactions with full recovery if a durable message log, like Howl is configured Spring fac
Page: Jencks 1.0 Release
Release Notes Welcome to the first major release of Jencks. We currently have support for working inbound JMS consumption using regular JMS transactions or full XA transactions with full recovery if a durable message log, like Howl is configured outbound
Page: Jencks 1.1 Release
Release Notes Welcome to the 1.1 release of Jencks. This release simplifies the configuration in Spring to work with newer versions of Spring and to avoid some possible issues with recursive configuration exceptions in Spring. Download Here Download Descr
Page: Jencks 1.1.1 Release
Release Notes Welcome to the 1.1.1 release of Jencks. This release is a bug fix release. Download Here Download Description jencks-1.1.1.zip Binary Distribution in zip package jencks-1.1.1-src.zip Source Distribution in zip package jencks-1.1.1.tar.gz Bin
Page: Jencks 1.2 Release
Release Notes Welcome to the 1.2 release of Jencks. This release is primarily a bug fix release but also includes moving to Maven 2 for the build and the release repository moving to use Apache ActiveMQ 4.0 Download Here Download Description jencks-1.2.ja
Page: Jencks 1.3 Release
Release Notes Welcome to the 1.3 release of Jencks. This release is primarily an upgrade to Geronimo 1.1. Download Here Download Description jencks-1.3.jar Code JAR jencks-1.3-sources.jar Source Distribution in a JAR jencks-1.3-javadoc.jar JavaDoc Distrib
Page: Jencks 2.0 Release
Release Notes Welcome to the 2.0 release of Jencks. This release is primarily an upgrade to Geronimo 1.2, but the JTA and JCA components have changed and are now much easier to configure. Download Here Download Description jencks-2.0.jar Code JAR jencks-2
|
K |
||||||||||||||||||||||||||||||
L |
MPage: Mailing ListsThe following mailing lists are available. List Name Subscribe Unsubscribe Archive GMane (for NTTP, news and blog viewing of archives) Jencks User List Subscribe Unsubscribe Archive GMane Jencks Developer List Subscribe Unsubscribe Archive GMane Jencks SC
Page: Message Driven POJOs
The JCA Java Connector Architecture provides the most efficient way of thread pooling, resource pooling, transaction handling and consumption on JMS and other Resource Adapters. For example if you are consuming JMS messages, the JCA container provides the
|
||||||||||||||||||||||||||||||
NPage: NavigationOverview Home News FAQ Site Requirements Download Community Discussion Forum Mailing Lists Contributing Site Team Documentation Message Driven POJOs Outbound JMS Outbound JDBC Transaction Manager Work Manager AMQPool JavaDocs Resource Adadptors ActiveMQ W
Page: News
Page: notcm The notcm branch of Jencks contains version of the main Jencks code base which has been updated to work with the experimental notcm Geronimo branch. The notcm branch of Geronimo contains a number of simplifications which vastly reduce the work required of
Page: notcm Connection Factory
For the Impatient The following creates a JDBC data source: {snippet:id=ds|lang=xml|url=http://svn.codehaus.org/jencks/branches/2.0/src/test/resources/org/jencks/samples/outbound/jencks-tranql.xml?rev=HEAD} or with XBeanhttp://docs.codehaus.org/images/ico
Page: notcm Connection Manager
For the Impatient The following creates a connection manager with a pool of up to 10 connections: {snippet:id=connectionManager|lang=xml|url=http://svn.codehaus.org/jencks/branches/notcm/src/test/resources/org/jencks/samples/outbound/jencks-tranql.xml?rev
Page: notcm JCAConnector
For the Impatient The following creates a JCA connection links the echoBean to the TestTopic: {snippet:id=jcaConnector|lang=xml|url=http://svn.codehaus.org/jencks/branches/2.0/src/test/resources/org/jencks/samples/inbound/activemq.xml?rev=HEAD} or with XB
Page: notcm JCAContainer
For the Impatient The following creates a JCA container with a 25 thread pool: {snippet:id=jcaContainer|lang=xml|url=http://svn.codehaus.org/jencks/branches/2.0/src/test/resources/org/jencks/samples/inbound/activemq.xml?rev=HEAD} or with XBeanhttp://docs.
Page: notcm JDBC Managed Connection Factory
For the Impatient The following creates a JDBC managed connection factory: {snippet:id=mcf|lang=xml|url=http://svn.codehaus.org/jencks/branches/2.0/src/test/resources/org/jencks/samples/outbound/jencks-tranql.xml?rev=HEAD} or with XBeanhttp://docs.codehau
Page: notcm Transaction Manager
For the Impatient The following creates a transaction manager with a default transaction timeout of 10 minutes and does not support XA recovery: {snippet:id=tm|lang=xml|url=http://svn.codehaus.org/jencks/branches/2.0/src/test/resources/org/jencks/samples/
|
OPage: Outbound JDBCJencks supports any API for inbound and outbound messaging (thanks to the JCA specification). So you can use Jencks to create an XA pool of JDBC connections. The following example shows how to configure a pooled XA based DataSource using Tranql. The POJO
Page: Outbound JMS
Jencks supports both Inbound JMS messaging as well as outbound messaging. Outbound messaging (or message outflow to use JCA speak) allows you to pool and reuse JMS sessions and connections when sending messages. In addition JCA takes care of associating i
|
||||||||||||||||||||||||||||||
P |
QPage: QuickLinksDownload | JavaDocs | Source | Wiki |IRC | IRC Log | Mailing Lists | Discussion Forum | Support
|
||||||||||||||||||||||||||||||
RPage: RequirementsIf you are already using Spring, to be able to use Jencks you just need the following jars on your classpath jencks-all.jar 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 i
|
SPage: SitePage: SiteIndex {index}{index}
Page: SiteMap
Page: Source Web Browsing of SVN To browse SVN via the web using this URL http://svn.codehaus.org/jencks/trunk/jencks/ Anonymous SVN access This project's SVN repository can be checked out through HTTP svn co http://svn.codehaus.org/jencks/trunk/jencks Updates from wi
|
||||||||||||||||||||||||||||||
TPage: TeamThis page lists who we are. By all means add yourself to the list... Committers Name ID Organisation Alan D. Cabrera maguro LogicBlaze Dain Sundstrom dain GlueCode David Blevins dblevins GlueCode David Jencks djencks GlueCode Guillaume Nodet gnt LogicBlaz
Page: Transaction Manager
Its quite common in Spring applications you want to deploy a JTA TransactionManager in your Spring.xml. To do this in Jencks add the following to your spring.xml {snippet:id=tm|lang=xml|url=http://svn.codehaus.org/jencks/trunk/jencks/src/test/resources/or
|
UPage: Using JencksQuestions on using Jencks
Page: Using Message Driven POJOs
|
||||||||||||||||||||||||||||||
V |
WPage: WebSphere6Susan Liebeskind did all the hard work to create this configuration for working with WebSphere6... Example XML
Page: What is the license
This software is open source using the Apache 2.0 licence (a liberal BSD style licence which is very commercial friendly)
Page: Why is the project called Jencks
The name Jencks comes from the daddy of JCA, David Jencks. David wrote most of the JBoss JCA and the Geronimo JCA containers and what David doesn't know about JCA is probably not worth knowing So given his immense contribution to the world of JCA we felt
Page: Work Manager
The J2EE/JCA specification provides a WorkManager interface which provides a J2EE compliant way of working with a thread pool, scheduling work and creating timerse. In enterprise environments & containers you often wish to setup the thread for security or
|
||||||||||||||||||||||||||||||
X |
Y |
||||||||||||||||||||||||||||||
Z |
!@#$ |
||||||||||||||||||||||||||||||
Labels
1 Comment
Hide/Show CommentsMar 17, 2012
Dianna Kelly