What is the status of the server integration code?

[starksm64]

I don't see any server integration code/descriptors in the jbossas codebase fo r the new jms stack. All that exists is the generic jms rar. The cts is pulling in a sar from its local codebase. I don't see why the integration services/descriptors are not in the jbossas/messaging module itself as this is a layer on top of the jms core that is jboss version specific.

[starksm64]

At a minimum, the unscoped sar needs to be out in the jboss repository.

[starksm64]

And the jboss-messaging-client.jar.
Right now http://repository.jboss.com/jboss/messaging/snapshot/lib/ is not usable.

[ovidiu.feodorov]

http://repository.jboss.com/jboss/messaging/snapshot is out of date. The release to be used with the AS is 1.0.1.GA: http://repository.jboss.com/jboss/messaging/1.0.1.GA

I could add an unscoped sar there, but it won't work unless we align our dependencies (especially Remoting).

[starksm64]

What goes into jboss5 must be an unscoped sar. That is what must be in the repository. There is also the question of why the sar should be in the messaging codebase as its a pure integration component that has dependencies on jbossas.

[ovidiu.feodorov]

Correct.

The way we do it now needs to be adjusted.

[starksm64]

The jbossas trunk messaging module has been copied to a jbossmq module to preserve the legacy codebase, and messaging has been stripped down to be used as the basis for the jboss-messaging sar/descriptors that should make up the server integration code.

[ovidiu.feodorov]

Thanks, I am taking over:

http://jira.jboss.org/jira/browse/JBMESSAGING-631
http://jira.jboss.org/jira/browse/JBMESSAGING-632

[ovidiu.feodorov]

Scott, I've taken a quick look at the AS head.

The most important thing is that dependencies are OK: Remoting 2.2.0.Alpha2, Serialization 1.0.3.GA.

I don't know exactly what "snapshot" means for AOP, but as long as is higher than 1.5.0.GA, Messaging should be fine.

In conclusion, there's is no reason not to have a fully working unscoped Messaging deployment.

I want to adjust the deployment descriptors under jboss-head/messaging so everything works. I plan to use customized copies in jboss-head/messaging/src/etc/..., as we discussed (http://jira.jboss.org/jira/browse/JBMESSAGING-632).


http://jira.jboss.org/jira/browse/JBMESSAGING-631 becomes obsolete if I do this, so I'll close it.


Will post here if I have questions.

[kabirkhan]

I don't know exactly what "snapshot" means for AOP, but as long as is higher than 1.5.0.GA, Messaging should be fine.

AOP 2.0.0.alpha2 is the target version

[ovidiu.feodorov]

I've completed the integration. JBM deploys unscoped under default/deploy/messaging (or all/deploy/messaging). The original deployment descriptors are stored in jboss-head/messaging/src/etc/deploy.

The only artifact required to be present in repository is jboss-messaging.jar.

Just update from the head and rebuild. I'll be standing by if you have any problems.