You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "jamesnetherton (via GitHub)" <gi...@apache.org> on 2023/02/27 08:15:37 UTC

[GitHub] [camel-quarkus] jamesnetherton opened a new issue, #4603: [Quarkus 3.0.0.CR1] CXF SOAP integration test failures

jamesnetherton opened a new issue, #4603:
URL: https://github.com/apache/camel-quarkus/issues/4603

   Something must have changed in Quarkus JAXB because all of the CXF SOAP tests fail with similar `Two classes have the same XML type` issues like this:
   
   ```
   java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
           [error]: Build step io.quarkus.jaxb.deployment.JaxbProcessor#setupJaxbContextConfig threw an exception: java.lang.IllegalStateException: Failed to configure JAXB context
           at io.quarkus.jaxb.deployment.JaxbProcessor.validateContext(JaxbProcessor.java:392)
           at io.quarkus.jaxb.deployment.JaxbProcessor.setupJaxbContextConfig(JaxbProcessor.java:317)
           at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
           at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
           at java.base/java.lang.reflect.Method.invoke(Method.java:568)
           at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
           at io.quarkus.builder.BuildContext.run(BuildContext.java:282)
           at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
           at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
           at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
           at java.base/java.lang.Thread.run(Thread.java:833)
           at org.jboss.threads.JBossThread.run(JBossThread.java:501)
   Caused by: org.glassfish.jaxb.runtime.v2.runtime.IllegalAnnotationsException: 47 counts of IllegalAnnotationExceptions
   Two classes have the same XML type name "{http://www.w3.org/2000/09/xmldsig#}ObjectType". Use @XmlType.name and @XmlType.namespace to assign different names to them.
           this problem is related to the following location:
                   at org.apache.cxf.ws.security.sts.provider.model.xmldsig.ObjectType
           this problem is related to the following location:
                   at org.apache.xml.security.binding.xmldsig.ObjectType
                   at public jakarta.xml.bind.JAXBElement org.apache.xml.security.binding.xmldsig.ObjectFactory.createObject(org.apache.xml.security.binding.xmldsig.ObjectType)
                   at org.apache.xml.security.binding.xmldsig.ObjectFactory
                   at protected java.util.List org.apache.xml.security.binding.xmldsig.TransformType.content
                   at org.apache.xml.security.binding.xmldsig.TransformType
                   at protected java.util.List org.apache.xml.security.binding.xmlenc.TransformsType.transform
                   at org.apache.xml.security.binding.xmlenc.TransformsType
                   at public org.apache.xml.security.binding.xmlenc.TransformsType org.apache.xml.security.binding.xmlenc.ObjectFactory.createTransformsType()
                   at org.apache.xml.security.binding.xmlenc.ObjectFactory
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-quarkus] zbendhiba closed issue #4603: [Quarkus 3.0.0.Alpha6] IllegalAnnotationsException Two classes have the same XML type name thrown at build time by quarkus-jaxb

Posted by "zbendhiba (via GitHub)" <gi...@apache.org>.
zbendhiba closed issue #4603: [Quarkus 3.0.0.Alpha6] IllegalAnnotationsException Two classes have the same XML type name thrown at build time by quarkus-jaxb
URL: https://github.com/apache/camel-quarkus/issues/4603


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-quarkus] jamesnetherton commented on issue #4603: [Quarkus 3.0.0.CR1] CXF SOAP integration test failures

Posted by "jamesnetherton (via GitHub)" <gi...@apache.org>.
jamesnetherton commented on issue #4603:
URL: https://github.com/apache/camel-quarkus/issues/4603#issuecomment-1460330965

   Just a heads up - in order to upgrade to Quarkus 3.0.0.Alpha5, I had to disable the cxf-soap test bits in https://github.com/apache/camel-quarkus/commit/c8a4adb958733134031323dc668bc37ef5c244f6.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-quarkus] ppalaga commented on issue #4603: [Quarkus 3.0.0.CR1] CXF SOAP integration test failures

Posted by "ppalaga (via GitHub)" <gi...@apache.org>.
ppalaga commented on issue #4603:
URL: https://github.com/apache/camel-quarkus/issues/4603#issuecomment-1446525037

   Blocked by https://github.com/quarkiverse/quarkus-cxf/issues/730


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-quarkus] ppalaga commented on issue #4603: [Quarkus 3.0.0.CR1] IllegalAnnotationsException Two classes have the same XML type name thrown at build time by quarkus-jaxb

Posted by "ppalaga (via GitHub)" <gi...@apache.org>.
ppalaga commented on issue #4603:
URL: https://github.com/apache/camel-quarkus/issues/4603#issuecomment-1462292305

   There is a proper fix in Quarkus main branch that did not make it to 3.0.0.Alpha5: https://github.com/quarkusio/quarkus/pull/31666
   
   With Quarkus 3.0.0.Alpha5 is issue can be worked around by putting `quarkus.jaxb.validate-jaxb-context=false` into application.properties. Let me prepare a PR. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-quarkus] ppalaga commented on issue #4603: [Quarkus 3.0.0.CR1] CXF SOAP integration test failures

Posted by "ppalaga (via GitHub)" <gi...@apache.org>.
ppalaga commented on issue #4603:
URL: https://github.com/apache/camel-quarkus/issues/4603#issuecomment-1446418740

   It looks like CXF 4 does not depend on santuario:xmlsec anymore. So quarkus-cxf should also stop depending on Qverse xmlsec. This is surely reproducible also in Qverse CXF.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [camel-quarkus] ppalaga commented on issue #4603: [Quarkus 3.0.0.CR1] CXF SOAP integration test failures

Posted by "ppalaga (via GitHub)" <gi...@apache.org>.
ppalaga commented on issue #4603:
URL: https://github.com/apache/camel-quarkus/issues/4603#issuecomment-1457881986

   > It looks like CXF 4 does not depend on santuario:xmlsec anymore. So quarkus-cxf should also stop depending on Qverse xmlsec.
   
   No, this is not true. The santuario:xmlsec dependecy is still there, although now it is transitive.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org