cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Ryder (JIRA)" <>
Subject [jira] Commented: (CXF-2750) Output parameter and method name issue
Date Thu, 01 Apr 2010 18:45:27 GMT


Derek Ryder commented on CXF-2750:

I wasn't recommending violating the spec and there is much to be said for knowing the spec
and thereby being aware that one cannot create method in such a manner. However I would be
in favor of an exception that provides more information to the developer using the tool.

> Output parameter and method name issue
> --------------------------------------
>                 Key: CXF-2750
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAXB Databinding
>    Affects Versions: 2.2.7
>            Reporter: Derek Ryder
> I discovered an issue related to the name of a method and it's associated output parameter
> 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  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.
You can reply to this email to add a comment to the issue online.

View raw message