[
https://issues.apache.org/jira/browse/CXF-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2750.
------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Daniel Kulp
This is more or less "fixed" as we pretty much require ASM now and if you have
ASM on the classpath, you get something like:
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of
IllegalAnnotationExceptions
Two classes have the same XML type name
"{http://cxf.apache.org/systest/jaxws/DocLitWrappedCodeFirstService}doMyFoo";.
Use @XmlType.name and @XmlType.namespace to assign different names to them.
> Output parameter and method name issue
> --------------------------------------
>
> Key: CXF-2750
> URL: https://issues.apache.org/jira/browse/CXF-2750
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.2.7
> Reporter: Derek Ryder
> Assignee: Daniel Kulp
> Fix For: 2.4
>
>
> I discovered an issue related to the name of a method and it's associated
> output parameter name.
> If you name the method foo and the output parameter is named fooResponse,
> you'll end up with an exception.
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'eSessionAuthenticationWS': Invocation of init method failed;
> nested exception is javax.xml.ws.WebServiceException:
> org.apache.ws.commons.schema.XmlSchemaException: Schema for namespace '<your
> name space>' already contains type 'fooResponse'
> I did some digging into the code and it appears to be an issue with the
> naming convention in the code. When generating the response object for an
> operation it takes the method name and adds Response to it and it ends up as
> a schema type. Then when the output parameter is being initialized there is
> already a fooResponse schema type and thus the schema type collision.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
