问题描述
在AIX平台上将ear文件部署到WLS 10.3时出现此错误。同样的耳朵在Windows / Linux平台上运行良好。
I get this error when deploying the ear file on to WLS 10.3 on AIX platform. The same ear works fine on Windows/Linux platforms.
Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
at weblogic.xml.jaxp.WebLogicDocumentBuilderFactory.newDocumentBuilder(WebLogicDocumentBuilderFactory.java:140)
at com.bea.security.xacml.policy.PolicyUtils.getRootNode(PolicyUtils.java:54)
at com.bea.security.xacml.policy.PolicyUtils.read(PolicyUtils.java:86)
at com.bea.security.providers.xacml.store.BasePolicyStore.getAbstractPolicy(BasePolicyStore.java:1251)
at com.bea.security.providers.xacml.store.BasePolicyStore.readPolicy(BasePolicyStore.java:1231)
at com.bea.security.providers.xacml.store.BasePolicyStore.readPolicy(BasePolicyStore.java:1114)
at com.bea.security.providers.xacml.entitlement.PolicyManager.listPolicies(PolicyManager.java:747)
at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.startDeployPolicies(DeployableAuthorizationProviderV2Helper.java:90)
at weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl.startDeployPolicies(XACMLAuthorizationProviderImpl.java:269)
at com.bea.common.security.internal.legacy.service.PolicyDeployerProviderImpl$V2Adapter.startDeployPolicies(PolicyDeployerProviderImpl.java:69)
at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$DeploymentHandlerImpl.<init>(PolicyDeploymentServiceImpl.java:143)
at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$DeploymentHandlerImpl.<init>(PolicyDeploymentServiceImpl.java:129)
at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$ServiceImpl.startDeployPolicies(PolicyDeploymentServiceImpl.java:97)
at weblogic.security.service.WLSPolicyDeploymentServiceWrapper$DeploymentHandlerImpl.<init>(WLSPolicyDeploymentServiceWrapper.java:70)
at weblogic.security.service.WLSPolicyDeploymentServiceWrapper$DeploymentHandlerImpl.<init>(WLSPolicyDeploymentServiceWrapper.java:60)
at weblogic.security.service.WLSPolicyDeploymentServiceWrapper.startDeployPolicies(WLSPolicyDeploymentServiceWrapper.java:40)
at weblogic.security.service.AuthorizationManager.startDeployPolicies(AuthorizationManager.java:489)
at weblogic.servlet.security.internal.WebAppSecurityWLS.<init>(WebAppSecurityWLS.java:72)
at weblogic.servlet.security.internal.ServletSecurityManager.<init>(ServletSecurityManager.java:39)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:464)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:901)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:345)
推荐答案
你的类路径可能很杂乱使用Xerces API的不同版本的JAR文件。清理类路径。在Web应用程序的情况下，这包括 Webapp / WEB-INF / lib ， Appserver / lib 和 / JRE / lib 文件夹。
Your classpath is likely cluttered with different versioned JAR files of the Xerces API. Cleanup the classpath. In case of a webapplication, this includes Webapp/WEB-INF/lib, Appserver/lib and /JRE/lib folders.
最常见的原因是你有不同版本的Xerces JAR遍布 Webapp / WEB-INF / lib 和 Appserver / lib 。假设appserver库中的那些是默认提供的和正确的版本，请删除webapp库中的那些。您不应该在webapp的库中拥有任何特定于appserver的JAR。
Most common cause is that you have different versioned Xerces JAR's spreading over the Webapp/WEB-INF/lib and Appserver/lib. Assuming that the ones in the appserver's library are the default-supplied and correct versions, get rid of those in the webapp's library. You should not have any appserver-specific JAR's in the webapp's library.
这篇关于XIncludeAwareParserConfiguration与XMLParserConfiguration不兼容的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！