[jboss-dev-forums] [Design of POJO Server] - Re: Missing org.jnp.server.NamingServer_Stub

[adrian@jboss.org]

"dimitris at jboss.org" wrote : 
  | BTW, now different issues show up, on of which is the missing jbossMQ classes, now that it was removed from trunk :-)
  | 

Which way around is this test?

I guess this is the 5.0.x testsuite (i.e. client side) running against a 4.2.x server?

The other way around wouldn't work either.
4.2.x doesn't include the jboss messaging jars. :-)

There's two likely solutions as far as I can see.
1) Disable the test for 5.0.x talking to older versions
(its still needed for future tests of JBoss Messaging compatiblity)
2) Include the jbossmq-client.jar from whatever version you are running against
when it is pre 5.0.x in the classpath

(2) Is what you would do for any other remote jms and it is also what
users will have to do if they want JBoss5 to use an older JBoss running jbossmq
as their JMS server.

Or a there's a third option which is to include a binary version
of jbossmq-client.jar from 4.2.x in the shared lib directory of JBoss5 
to make things easier for users (although its not exactly rocket
for them to copy it across themselves. :-)

The downside of the third option is that it introduces a permenant dependency
on concurrent.jar (jbossmq still uses it) which I think we'd like to get rid of
at some point soon.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191859#4191859

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191859