After more investigations, it seems that the problem comes from one component (I don't
know which) of JBossESB. I have made a small test case that works in the standard JBoss
release and not in Jboss with JbossESB 4.2.3.
I post it on the JBossESB forum.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231854#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...