2 Replies Latest reply on Dec 7, 2005 9:30 AM by Adrian Brock

    JBoss ASF - ServerSessionPool - replace with JCA1.5

    Adrian Brock Master

      If we complete the testing of the generic jms inbound resource adapter
      and properly structure it for plugins (i.e. allow people to change the behaviour)
      we can get rid of JBoss ASF.

      Except in jboss-3.2.x which doesn't have JCA1.5, but I would even backport
      JCA1.5 if that was necessary :-)

      Task to be completed:
      http://jira.jboss.com/jira/browse/JBAS-1434
      and previous discussion thread.
      http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672

      This also makes sense for our POJO strategy, since JCA1.5 effectively allows
      anything to be a MessageEndpointFactory whether it is an MBean or a POJO.
      See also:
      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70511
      http://jira.jboss.com/jira/browse/JBAS-1433

      Additionally it eases EJB3's integration task
      http://jira.jboss.com/jira/browse/JBAS-2409
      http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73265

      Since this has cross-cutting issues, I think the priority of JBAS-1434 should be
      increased. Tim is currently assigned, but he is busy on JBoss Messaging.

        • 1. Re: JBoss ASF - ServerSessionPool - replace with JCA1.5
          Tim Fox Master

          I for one would love to see the back of ASF.

          It's whole way of working doesn't really fit with the normal connection, session, consumer approach and getting it to work with our jms facade architecture has cause us to pollute the api somewhat.

          I think we should definitely aim to get the inbound RA tested before the 1.0 messaging release, so we can ship messaging without this abomination.

          AFAIK the other major vendors either don't provide an implementation of ASF at all, and if they do they certainly don't use it to implement MDB concurrency - it's just provided as facilities that can be used by the "expert jms developer" in their own apps.

          I'm up to eyeballs in other stuff right now, but I agree this would be a good one to get done asap.

          • 2. Re: JBoss ASF - ServerSessionPool - replace with JCA1.5
            Adrian Brock Master

             

            "timfox" wrote:

            I think we should definitely aim to get the inbound RA tested before the 1.0 messaging release, so we can ship messaging without this abomination.


            There is a need to do it now, to get rid of the "abomination" ;-)
            of the EJB3 integration which has forked part it and done some
            brain deaths along the way.

            e.g.
            <activation-config-property name="resourceAdapterName"/>
            

            Completely unportable!

            and some of the config properties use different names to what is already done
            by the JMS RA inbound.

            The whole thing is just a mess (and all for want of some pre-discussion and
            synching/validation of ideas before releasing it).