It should be in the client deployment classpath metadata, but its not used by the
ClientLauncher currently. Using the mc and vfs class loader in the ClientLauncher was what
I was starting to work on when the jndi name issues came up.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149616#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...