[
https://issues.apache.org/jira/browse/CXF-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832691#action_12832691
]
Daniel Kulp commented on CXF-2646:
----------------------------------
I think it's both a JAXB issue and a WSDL4J issue. If you look in wsdl4j, you
see:
protected Map messages = new HashMap();
protected Map bindings = new HashMap();
protected Map portTypes = new HashMap();
protected Map services = new HashMap();
Basically, everything is stored in a non-linked HashMap. Thus, no guaranteed
ordering.
It gets even more complicated when doing Sun and IBM jdks as the IBM JDK
returns a lot of things in a different order. The properties in the sequences
would likely be reversed, etc....
In anycase, this is why a while ago, we changed all the CXF unit tests from
using straight string compares of the wsdl's to doing either a token based
compare or using xpaths to check for specific things the tests are trying to
check.
> java2ws produces different wsdl files depending on the JDK in use
> -----------------------------------------------------------------
>
> Key: CXF-2646
> URL: https://issues.apache.org/jira/browse/CXF-2646
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.2.6
> Reporter: Benson Margulies
> Attachments: cxf-tc.jar, linux15.wsdl.canon, linux16.wsdl.canon
>
>
> With the attached test case,
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
> and
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02)
> Java HotSpot(TM) Client VM (build 1.5.0_19-b02, mixed mode, sharing)
> produce different wsdls. This is not good for regression testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
