-
1. Re: classloader problem?
marklittle Aug 8, 2007 10:36 AM (in response to jw)Can you show me the code that you use to populate the message you're sending? Is it an ESB-aware client, for example?
-
2. Re: classloader problem?
claudio_br Aug 8, 2007 10:54 AM (in response to jw)Try to create the message with MessageType.JAVA_SERIALIZED, but ClassA must implements Serializable
-
3. Re: classloader problem?
jw Aug 8, 2007 11:05 AM (in response to jw)Hi Mark
The message comes through the gateway. So | just write a normal JMS Object Message to the queue the gateway is listening. -
4. Re: classloader problem?
marklittle Aug 8, 2007 11:57 AM (in response to jw)So if I'm understanding you correctly, you're using the standard JMS Gateway? Do you provide your own JMS composer implementation?
The standard gateway composer creates a default Message, which is XML. Can you also confirm (by calling Message.getType()) that you're dealing with an XML implementation? -
5. Re: classloader problem?
marklittle Aug 8, 2007 12:18 PM (in response to jw)BTW, just so we're clear, when you said:
Serializing message.getBody().get() and deserializing it into a solves the problem (but that must be only a workaround).
What precisely did you do? -
6. Re: classloader problem?
marklittle Aug 8, 2007 8:43 PM (in response to jw)Can you also try the following: set org.jboss.soa.esb.message.default.uri in the "core" section of the ESB property file to urn:jboss/esb/message/type/JAVA_SERIALIZED and rerun your example.
-
7. Re: classloader problem?
jw Aug 9, 2007 4:43 AM (in response to jw)Hi Mark
Hot deplyment was the problem. It works after a restart.
Just to answer your questions:So if I'm understanding you correctly, you're using the standard JMS Gateway?
yesDo you provide your own JMS composer implementation?
noCan you also try the following: set org.jboss.soa.esb.message.default.uri in the "core" section of the ESB property file to urn:jboss/esb/message/type/JAVA_SERIALIZED and rerun your example.
has no effect. message.getType() is always XML (but that's not a problem for me).
Thanks for help
Juerg -
8. Re: classloader problem?
marklittle Aug 9, 2007 5:14 AM (in response to jw)So this wasn't an issue with JBossESB? I just want to be sure we don't miss something in the next GA release. Thanks.
-
9. Re: classloader problem?
jw Aug 9, 2007 5:35 AM (in response to jw)no, I think it's a 'hot deployment side effect' and not an ESB problem.
-