[jboss-dev-forums] [Design of JCA on JBoss] - Re: JCA antipattern? Or not?

[weston.price@jboss.com]

anonymous wrote : 
  | Also the JBoss JCA layer only provides message inflow for JMS AFAIK so this wan't an option for them either. 
  | 

This is not correct. JCA allows for generic inflow and is not limited to JMS based messaging. We have a few examples of generic inflow, most notably our Mail and Quartz RARs that provide this capability.  

If the client truly does not want to use MDB's then *any* solution for them will be non-standard whether they are using Spring or not. EE environments rely on the MDB (not necessarily JMS) mechanism to implement inflow and message driven listeners. 

Having said that, the only real 'hardwire' that forces the use of an MDB (which I just don't see as being that big of a deal, especially with EJB3), is the deployment. Currently there is no way to deploy a POJO listener and hook it up to a RAR. 

Having said this, they would still need to write a custom RA to handle the inflow and delivery for their specific messaging type.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020773#4020773

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020773