Forum Discussion
tstmartin
11 years agoContributor
Summary I got from our developers -
prior to Java7/J2EE5/WL12 Weblogic generated the soap response in A-Z (ignore case) order by default;
J7/J2EE5/WL12 generates in A-Z(case sensitive) order by default.
The annotation @XmlAccessorOrder(XmlAccessOrder.ALPHABETICAL) should generate the A-Z(case sensitive) wsdl, but for some
reason did not.
Our build included a wsgen setting of xendorsed="true" ; changing this setting to 'false' allows the annotation to be honored and
the result is a case sensitive wsdl which we use on the client side to validate against the WS response.
Apologies I dont have the time or understanding to post a better explanation; hopefully there are enough clues there to help the next person who hits this.
-tom
prior to Java7/J2EE5/WL12 Weblogic generated the soap response in A-Z (ignore case) order by default;
J7/J2EE5/WL12 generates in A-Z(case sensitive) order by default.
The annotation @XmlAccessorOrder(XmlAccessOrder.ALPHABETICAL) should generate the A-Z(case sensitive) wsdl, but for some
reason did not.
Our build included a wsgen setting of xendorsed="true" ; changing this setting to 'false' allows the annotation to be honored and
the result is a case sensitive wsdl which we use on the client side to validate against the WS response.
Apologies I dont have the time or understanding to post a better explanation; hopefully there are enough clues there to help the next person who hits this.
-tom