Sorry - I don't know anything about Maven, we don't use it.
JBM should work out of the box with JBosss 5 beta 3 - it's the default JMS provider.
What classpath are you using that doesn't work?
For this context, maven is like ant. Difference being that it will try to contact a maven repository on the internet and download the dependencies if they don't exist locally. I am telling maven to look locally.
My classpath is:
I'm using a build.xml from the messaging 1.4.1.Beta1 download as a template, but there are some inconsistencies with jboss5. The code below is taken from jboss-messaging-1.4.1.Beta1\examples\topic\build.xml:
The above file does not exist in the /server/default/lib directory
The above folder (jboss-aop...) does not exist in the deploy directory due to the "deployer" folder structure of jboss5.
Same as previous entry.
As a result, I scavenged for these files elsewhere in jboss5. With the classpath described at top, I get the following:
I expect this is a classpath issue related to version mismatch. But if what's rolled in with jboss5 isn't sufficient, I don't know where next to look.
Any thoughts on what jars should (not) be included? I would be very happy to see code similar to the jboss-messaging examples, but verified to work with jboss5 beta3. Anybody know of such code?
Thanks for your help in this matter.
You're taking jboss-all-client from JBoss 3.2.3??
The classpath you quote should certainly work, you're probably just pulling in wrong versions of those files though.
To verify this, take Maven out of the picture and _manually_ get those jars from the distro. You should find that that works fine.
It would not work while using jboss-messaging-client version 1.4.1.Beta3. The boot of jboss indicates that it's using jboss-messaging version 1.4.0.SP1. I downloaded 1.4.0.SP1 version and used the messaging-client from this, and it now works as expected.
Should these versions be compatible with one another or not? That is; should a 1.4.0 server support 1.4.1+ clients (and vice versa)? I can't say for certain that they don't, but in my case they did not.
Thank you for your prompt response to my issue. Your team is doing a great service to the community.