[jira] Commented: (CXF-1396) Aegis + JAX-WS + @WebParam leads to schema type name conflicts

["Daniel Kulp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575149#action_12575149 ] 

Daniel Kulp commented on CXF-1396:
----------------------------------


Ummm...  why is it using a WebParam annotation to name a type?   Type names come from the classname of the param.  WebParam defines the element name (or part name for rpc).   

Is there a (disabled) testcase that shows this?



> Aegis + JAX-WS + @WebParam leads to schema type name conflicts
> --------------------------------------------------------------
>
>                 Key: CXF-1396
>                 URL: https://issues.apache.org/jira/browse/CXF-1396
>             Project: CXF
>          Issue Type: Bug
>          Components: Aegis Databinding
>            Reporter: Benson Margulies
>            Assignee: Dain Sundstrom
>             Fix For: 2.1
>
>
> In my application, when I try to run java2ws, I get:
> JavaToJS Error : java.lang.RuntimeException: Schema for namespace 'http://demo1.searchtools.basistech.com' already contains type 'argument
> The RuntimeException results directly from XML Schema, complaining about a name conflict on types.
> However, if I pull the wsdl with ?wsdl, there are no types at all named 'argument'.
> Thus I reason that the internally generated XML is quite different. I'm using aegis as a data binding.
> I fear that something is wrong with the code for java2 for aegis.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.