You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jeff Melby (JIRA)" <ji...@apache.org> on 2010/02/04 17:04:27 UTC
[jira] Created: (CXF-2653) autoNameResolution produces inconsistent
results
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
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.
[jira] Commented: (CXF-2653) autoNameResolution produces
inconsistent results
Posted by "Jeff Melby (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829708#action_12829708 ]
Jeff Melby commented on CXF-2653:
---------------------------------
Understood... we are currently just committing the stub code generated one way, but that is obviously not ideal.
> 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
>
> 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.
[jira] Resolved: (CXF-2653) autoNameResolution produces
inconsistent results
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-2653) autoNameResolution produces
inconsistent results
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829647#action_12829647 ]
Daniel Kulp commented on CXF-2653:
----------------------------------
I'm pretty sure there is nothing we can do about this. JAXB calls into the ClassNameAllocator in any order it feels like calling it and there isn't any information passed in that provides any type of locality that we could use. The method signature is just:
public String assignClassName(String packageName, String className);
We just record the names that have been already allocated and increment if there is a conflict.
In general, if you need direct control over the names, it is recommended to use a binding file to rename one of the classes.
> 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
>
> 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.