You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.
Using webservices-rt:2.4.3, I noticed a class conflict issue, when using together with e.g., xmlsec:2.0.6.
For example the package org.apache.xml.security.utils.resolver is 1-to-1 copied into webservices-rt, but with another version for many classes. This means that I can compile the project, but if I try to access a class at an incompatible point at runtime and the class from webservices-rt has been loaded instead that of xmlsec, I will get a runtime exception (e.g., NoSuchMethodError).
Note: the same package is included in java.xml.crypto (JDK 11), but it is shaded under com.sun, thus there is no conflict.
If I understand correctly, this is a general issue, which encapsulates #43.
Using
webservices-rt:2.4.3
, I noticed a class conflict issue, when using together with e.g.,xmlsec:2.0.6
.For example the package
org.apache.xml.security.utils.resolver
is 1-to-1 copied intowebservices-rt
, but with another version for many classes. This means that I can compile the project, but if I try to access a class at an incompatible point at runtime and the class fromwebservices-rt
has been loaded instead that ofxmlsec
, I will get a runtime exception (e.g.,NoSuchMethodError
).Note: the same package is included in
java.xml.crypto
(JDK 11), but it is shaded undercom.sun
, thus there is no conflict.If I understand correctly, this is a general issue, which encapsulates #43.
Example exception:
The text was updated successfully, but these errors were encountered: