Non-deterministic definition of default namespace @XmlSchema(namespace=...) in package-info.java about jaxb-ri HOT 2 CLOSED

@lukasj After we upgraded from JAXB-RI 4.0.2 to 4.03 we started getting form=qualified added to all our xsd elements that are generated using the com.sun.xml.ws:jaxws-maven-plugin. We don't find anything in the JAXB-RI release notes that seem related, but we stumbled on this change and It seems like it could be related. Do you know of a way to stop that from happening?

I've tried adding the following to the package-info.java

@jakarta.xml.bind.annotation.XmlSchema (
elementFormDefault= XmlNsForm.UNQUALIFIED
)

For example using JAXB-RI 4.0.3 "element1" has form="qualified"...

<xs:element name="element1" type="xs:string" form="qualified" nillable="true" minOccurs="0" maxOccurs="unbounded"/>

If I move back to JAXB-RI 4.0.2 then form="qualified" is gone.

<xs:element name="element1" type="xs:string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>

I am aware that it is recommended to qualify all elements, but I am hesitant to inform all of our clients as it would require them to modify their SOAP requests, and I fear the potential backlash that could result from it.

from jaxb-ri.

that regression is now fixed

from jaxb-ri.