-
1. Re: CXF JAR conflict Exception: "WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.JAXBElementProvider"
zidoff May 17, 2018 1:12 PM (in response to zidoff)Hi
I resolved the problem by adding the follow deployment descriptor: (jboss-deployment-structure.xml) under TEST.ear\META-INF:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
<deployment>
<exclude-subsystems>
<subsystem name="jaxrs" />
</exclude-subsystems>
</deployment>
</jboss-deployment-structure>
Best Regards
-
2. Re: CXF JAR conflict Exception: "WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.JAXBElementProvider"
hohwille Aug 21, 2018 11:16 AM (in response to zidoff)Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,5]
Message: WFLYSRV0174: Unexpected content of type 'element start', name is '{urn:jboss:deployment-structure:1.0}exclude-subsystems', text is: 'null'
at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser10.unexpectedContent(JBossDeploymentStructureParser10.java:874)
Suggested XML does not work (JBoss EAP 7):
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,5]
Message: WFLYSRV0174: Unexpected content of type 'element start', name is '{urn:jboss:deployment-structure:1.0}exclude-subsystems', text is: 'null'
at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser10.unexpectedContent(JBossDeploymentStructureParser10.java:874)