"scott.stark(a)jboss.org" wrote : "adrian(a)jboss.org" wrote : | | I suppose I could validate the capabilities that say they "ExportPackages" | | by running the ExportALL processing even if you explicitly list the package capabilities, | | but I'm not sure it really buys much? | | You'll still get a ClassNotFoundException on javax.jms.Queue | | if you export the package, include it in your filesystem but don't have that class. ;-) | Right, but what we want to be able to debug is the question about why javax.jms.Queue is not found when it sitting in my-jms.jar of classloader x. Its going to be common to have classes from the server domain hidden from the application deployment class loader, so why the hidden class is not seen in the question. | The management interface of the classloader will show the package is not exported, but you'd need to see the filter(s) and decode them to understand why. I guess I could always add some more trace logging to say which filter excludes a package? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131488#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...