I am using a plugin environment on the client that provides classloader separation for each plugin. This leads to a problem in the UnfiledMetaData class where it stores the context classloader when it is created. My web service interface is coming from a different plugin, thus a different ClassLoader. When attempting to load the interface class, the UnfiledMetaData is using its stored ClassLoader instead of the current context ClassLoader. Could someone please tell me what reasoning is for storing the classloader in the UnfiledMetaData object, and is there some way to get the correct ClassLoader into the UnfiledMetaData? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056448#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...