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
JAXB-API propagates opennes to implementation module in a way that if a module is open to java.xml.bind it should be also open to an implementation for example com.sun.xml.bind.
Problem arises when classes used as root element properties are from other package than root elements.
If above classes are declared in a module com.app and that module declares openness to java.xml.bind' as suggested by JAXBContext#newInstance` javadoc:
module com.app {
requires java.xml.bind;
opens com.foo to java.xml.bind;`
opens com.bar to java.xml.bind;
}
Then if JAXB is called with JAXBContext.newInstance(A.class);, JAXB API propagates openness of com.foo to com.sun.xml.bind however it doesn't scan classes for JAXB annotations during SPI discovery and so fails to propagate openness for com.bar.
The text was updated successfully, but these errors were encountered:
JAXB-API propagates opennes to implementation module in a way that if a module is open to
java.xml.bind
it should be also open to an implementation for examplecom.sun.xml.bind
.Problem arises when classes used as root element properties are from other package than root elements.
If above classes are declared in a module
com.app
and that module declares openness tojava.xml.bind' as suggested by
JAXBContext#newInstance` javadoc:Then if JAXB is called with
JAXBContext.newInstance(A.class);
, JAXB API propagates openness of com.foo tocom.sun.xml.bind
however it doesn't scan classes for JAXB annotations during SPI discovery and so fails to propagate openness forcom.bar
.The text was updated successfully, but these errors were encountered: