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: http://camel.465427.n5.nabble.com/Camel-JCA-tp4264706p4264706.html Sent from the Camel - Users mailing list archive at Nabble.com.
