Class javax /xml /rpc /encoding /TypeMappingRegistry violates loader constraints

[Askar Kalykov]

I have web service MyService on server side and two clients on my computer. Clients are webapps and have the same service-stub.jars; one of them starts sucessfully and another throws exception below:

SEVERE: Exception sending context initialized event to listener instance of class myservice.MyServletContext
java.lang.LinkageError: Class javax/xml/rpc/encoding/TypeMappingRegistry violates loader constraints
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1626)
        at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:850)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1299)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1181)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at myserviceclient.MyService_SerializerRegistry.getRegistry(MyService_SerializerRegistry.java:26)
        at myserviceclient.MyService_Impl.<init>(MyService_Impl.java:25)
        at myservice.MyServletContext.contextInitialized(MyServletContext.java:25)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3637)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4073)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:800)
        at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:695)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1106)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1019)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1011)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:440)
        at org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)

Both applications cunstructs their stubs in ServletContextListener.contextInitialized() with this code:

            ServletContext app = sce.getServletContext();
            String uri_address = app.getInitParameter("uriAddress");
            Stub stub = (Stub)(new MyService_Impl()).getMyIFPort();

I don't really understand what's the point..

[Rick Fischer]

I am having the same problem. Did you ever get this resolved?

[Campbell Moss]

See http://www.coderanch.com/t/128344/XML/Class-violates-Loader-COnstraints

I managed to fix this error by removing all classes under the javax package from the .war file - these should be in the app server's classpath anyway, so shouldn't need to be in the deployed package.