[jesper.pedersen]

We need to target the adaptor implementation towards JBM 1.4 as it is deployed in AS 5.0 and EAP 4.3.

An implementation for JBM 2.0 would happen at a later point.

Looking at other projects - ActiveMQ and JORAM - they include an adaptor in their distribution so I think we should go this way also - e.g. as a sub-project in JBM.

Then we can remove the existing JCA/JMS code in AS/trunk as JBossMQ isn't used anymore.

There are properly some code that can be shared, but lets look at that at a later point when the implementation is more or less complete.

I'll get something up and running and we can look into importing it into JBM SVN.

[adrian.brock]

"jesper.pedersen" wrote:

Then we can remove the existing JCA/JMS code in AS/trunk as JBossMQ isn't used anymore.

No, we are need to provide a generic JMS adapter for people that use a thirdparty jms
that has no resource adapter of its own. e.g. Tibco

NOTE: People can still use JBossMQ with JBoss5 if they configure it themselves.

[jesper.pedersen]

Ok - so basically leave as is -- will do.

[timfox]

"jesper.pedersen" wrote:
We need to target the adaptor implementation towards JBM 1.4 as it is deployed in AS 5.0 and EAP 4.3.

My comments about a JBM specific RA were referring to JBM 2.0 only. There's no way we're going to do this on the EAP 4.3 / AS 5 timescale. (EAP 4.3 code freeze has already started!).

To fix the EAP 4.3 bug, the current generic JMS RA needs to be patched so it doesn't make erroneous assumptions of XA capability based on instanceof.

[timfox]

And as Adrian also mentioned, you'll still need a generic JMS RA anyway to work with other JMS systems that don't provide their own RA and provide a connection consumer.

[vickyk]

We need something generic as this
https://genericjmsra.dev.java.net/

I think the existing JMS ra can be generic but is based on many assumptions .

[timfox]

"vickyk" wrote:
We need something generic as this
https://genericjmsra.dev.java.net/

I think the existing JMS ra can be generic but is based on many assumptions .

Looks like this thread is diverging into several different topics

1) Implementation of a JBM specific RA using an internal API. This is really a sub project of JBM and won't happen until JBM 2.0

2) Fixing the instanceof bug in the current pseudo-generic JMS RA.

3) Improving the current pseudo-generic resource JMS RA to work with providers that don't provide a connection consumer. Looks like the glassfish one deals with this by doing synchonrous receives.

I would suggest each of these are spun off into separate threads...

[jesper.pedersen]

Agreed - focus is now on 2)

1) + 3) will happen after AS-5.0.GA.

I'll kick off the separate threads when the focus switches.