"adrian(a)jboss.org" wrote :
| I think I know what the bug is with messaging. :-)
|
| The "export all" handling isn't picking up the default package, so the
classloader
| for jboss-messaging.jar isn't included in the index of classloaders to check
| for Thread.currentThread().getContextClassLoader().getResource("VERSION");
|
I fixed the "default package" problem, but it is still failing to deploy jms.
Strangely, it doesn't always fail? But it does more often than not.
Having looked at the code, I don't think this is a classloader issue
unless it is a problem with the new aop integration that Kabir did
i.e. it is not applying the correct advices.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119169#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...