-
1. Re: JBoss ASF - ServerSessionPool - replace with JCA1.5
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
"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).