Thanks. I removed jboss-messaging-client.jar from my ear and replaced it with
jboss-messaging.jar. I then get the following:
| 2007-04-27 09:17:36,308 ERROR [com.eLynx.BPM.Message.JmsMessageService]
Exception sending Jbpm message
| java.lang.RuntimeException: Failed to download and/or
I appreciate your quick response. It is good to hear that you are working to
eliminate the need for scoping. I tried putting the jar you specified in my
lib directory and restarting JBossAS (4.0.5, ejb3 configuration) and It gives
the following exception:
| 2007-04-26 08:52:40,253 DEBUG
Well, I downloaded JBossAS 4.2.0.CR2, unzipped it, ran JBM 1.2.0 SP1 installer
against it. I then copied the new jboss-remoting.jar file into the lib
directory as well as all my services and apps except the webapp that has the
jboss-messaging-client.jar file. I then started the server and
One more thing. I added jboss-app.xml to meta-inf in my .ear file with:
jboss-app
| loader-repositoryjboss.messaging:loader=ScopedLoaderRepository
|
loader-repository-configjava2ParentDelegaton=true/loader-repository-config
|/loader-repository
| /jboss-app
|
This
Having to deploy scoped is a known PITA, and can be very fiddly in certain
situations.
Also the fat jboss-messaging-client.jar introduces other issues with versions
of dependencies.
Our #1 source of support cases is I am having classloader issues with
messaging. These are almost always
Thanks Tim.
We don't currently have support but I am working on getting it. I guess in the
mean time I will 'fiddle' as you say. You mentioned the fat
jboss-messaging-client.jar. Is there an alternative, say a thin or trim or
perhaps lean messaging-client.jar that can be assembled by me?
The thin jboss-messaging-client.jar will just contain the
org.jboss.messaging.* classes.
The rest of the stuff in there will already be present in the app server
probably.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041160#4041160
Reply to the post :
We are working towards eliminate needs of scoping for JBossMessaging.
I believe if you upgrade jboss-remoting.jar by this one:
http://repository.jboss.com/jboss/remoting/2.2.0.SP2/lib/jboss-remoting.jar
If you synchronize all your jar versions with the ones on jboss-messaging.sar I
think you
