camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tobeand <>
Subject Re: Camel JCA
Date Mon, 11 Apr 2011 04:11:24 GMT
In the JCA 1.5 specification, the message activation need a
ActivationSpec and a MessageEndpointFactory, ActivationSpec is used to
provide parameters to the adapter, the parameter values are defined in
MDB's ejb-jar.xml; MessageEndpointFactory is used to create
MessageEndpoints, and the MessageEndpoint is a dynamic proxy to the

If you want use JCA message inflow without MDB, you need to define
your mechanism of message activation and deactivation, including how
to pass parameters to adapter and how to invoking a listener's method.
You may need implement your own ActivationSpec, MessageEndpointFactory
and MessageEndpoint.

On Sat, Mar 26, 2011 at 3:41 AM, stuplarosa <> wrote:
> I'm writing a JCA resource adapter for a proprietary protocol.  This is an
> inbound JCA adapter that needs to receive the proprietary protocol, decode
> it, and invoke methods on EJBs.
> For other reasons, I have a Camel component for this protocol, so it seems
> logical to build an adapter by pairing it with the camel-ejb endpoint.
> Any thoughts about the architecture for such a resource adapter?  Most
> adapters dispatch to MDBs.  Would it make sense to bypass MDBs and use the
> EJB endpoint to invoke methods directly?  Would it be better to pass the
> incoming stream to an MDB and invoke the route there?
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

View raw message