[problem description]
<19-may-2008 09h05' cest> 'mobile-marketing'.
weblogic.application.moduleexception:
at weblogic.servlet.internal.webappmodule.startcontex ts(webappmodule.java:950)
at weblogic.servlet.internal.webappmodule.start(webap pmodule.java:353)
at weblogic.application.internal.flow.modulestatedriv er$3.next(modulestatedriver.java:204)
at weblogic.application.utils.statemachinedriver.next state(statemachinedriver.java:26)
at weblogic.application.internal.flow.modulestatedriv er.start(modulestatedriver.java:60)
truncated. see log file for complete stacktrace
java.lang.linkageerror: loader constraints violated when linking javax/xml/namespace/qname class
at com.sun.xml.bind.v2.model.impl.runtimebuiltinleafi nfoimpl.<clinit>(runtimebuiltinleafinfoimpl.java:186)
at com.sun.xml.bind.v2.model.impl.runtimetypeinfoseti mpl.<init>(runtimetypeinfosetimpl.java:25)
at com.sun.xml.bind.v2.model.impl.runtimemodelbuilder .createtypeinfoset(runtimemodelbuilder.java:84)
at com.sun.xml.bind.v2.model.impl.runtimemodelbuilder .createtypeinfoset(runtimemodelbuilder.java:41)
at com.sun.xml.bind.v2.model.impl.modelbuilder.<init> (modelbuilder.java:104)
truncated. see log file for complete stacktrace
[suggestion by david.turing]
when the same class is loaded from two different classloader(weblogic system classloader and application classloader), we will encountering this problem.
i am sure that weblogic use javax/xml/namespace/qname class and your version could be different at the build time.
i found that javax.xml.namespace.qname locate in 3 jar in weblogic 10:
so could you please replace the your original jar that contains the javax.xml.namespace.qname with d:\bea100\wlserver_10.0\server\lib\api.jar
and then rebuild your application.
then try to redeploy again.