[jboss-dev-forums] [Design of EJB 3.0] - Re: JBAS-2408 - EJB3 / JCA integration

[adrian@jboss.org]

The correct fix for this is for JCA to provide an AbstractMessageEndpointFactory
and "MessageEndpointInterceptor" (you actually need two for the two different models
AOP or JMX, but they can share a lot of code).

All the EJB2/3/POJO containers should do is provide callbacks for
things like isDeliveryTransacted(Method), getTransactionTimeout(Method)
and the dispatch interceptor (i.e. invoke the ejb container or pojo).

This work is also tied up with the JCA metadata repository.

"jesper.pedersen" wrote : 
  | I can see two areas that would benefit the implementation: 
  | 
  | 1) The TODO in JBossMessageEndpointFactory::resolveResourceAdapter about the creation of the ObjectName for the RA - is this still valid ?
  | 

This should be replaced with the container passing the above mentioned callback
to the JCA metadata repository.


  | 2) The use of JMSProviderAdapter in MessagingContainer which add a JAR dependency - we can just move this class to the ejb3 namespace
  | 

No. EJB3 is not the place for integration code. All EJB3 cares about is
I want to activate an endpoint with 
* this callback
* these activation config properties 
* some selection parameters to determine the rar, e.g. listener interface, rar name, etc.

There a lot of other threads about this with more details in either the JCA forum
and possibly the EJB3 or JMS forums?

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

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