Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Metro in place of Weblogic Webservices Stack
    text
    copied!<p>I am attempting to use Metro web services in place of the default Weblogic webservices stack contained in weblogic.jar.</p> <p>The problem comes when trying to get WebLogic to use the metro stack before its own.</p> <p>The steps I have taken so far is to reference the webservices-rt.jar in the project. So far I am getting this error while deploying the ear file....</p> <p>Caused By: java.lang.LinkageError: loader constraint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, javax/xml/datatype/DatatypeConstants, and the class loader (instance of ) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type</p> <p><strong>UPDATES:</strong></p> <p>Most Recent Error is: "class javax.xml.namespace.QName has neither @WebSerivce nor @WebServiceProvider" Strange that it is looking for @Webservice on a QName object:</p> <ol> <li>Contents of Application-Weblogic.xml</li> </ol> <p><code> &lt;wls:prefer-application-packages&gt;<br> &lt;wls:package-name&gt;com.ctc.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.xml.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.istack.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.datatype.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.driver.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.grammar.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.reader.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.relaxns.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.scanner.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.util.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.verifier.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.msv.writer.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.org.apache.xml.internal.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;com.sun.wsit.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.jws.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.bind.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.soap.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.stream.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.ws.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.activation.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.annotation.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.mail.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.security.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.registry.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.rpc.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javax.xml.crypto.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;javanet.staxutils.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;jp.gr.xml.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.codehaus.stax2.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.glassfish.gmbal.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.iso_relax.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.jcp.xml.dsig.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.jvnet.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.relaxng.</em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;antlr.<em>&lt;/wls:package-name&gt;<br> &lt;wls:package-name&gt;org.apache.commons.lang.</em>&lt;/wls:package-name&gt;<br> &lt;/wls:prefer-application-packages&gt;<br> </code></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload