[
https://issues.apache.org/jira/browse/CXF-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2653.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
I'm going to resolve this as "Won't Fix", but it's really a "Cannot Fix".
The workaround is for you to create a jaxws/jaxb binding file that would remap
one of the conflicting classes to a new and consistent name and not use the
autoNameResolution flag.
> autoNameResolution produces inconsistent results
> ------------------------------------------------
>
> Key: CXF-2653
> URL: https://issues.apache.org/jira/browse/CXF-2653
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.1.3
> Reporter: Jeff Melby
> Fix For: Invalid
>
>
> Using the -autoNameResolution option in WSDLToJava produces inconsistent
> results in the naming of classes for the same wsdl. Specifically, on one
> developer machine, it names one class GetMemberCHResponse and another
> GetMemberCHResponse2, but for another developer, these classes are reversed
> such that GetMemberCHResponse = GetMemberCHResponse2 and vice versa for
> developer #2. This is a problem when trying to interact with the stub code
> from the application code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
