[
https://issues.apache.org/jira/browse/CXF-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560190#action_12560190
]
Benson Margulies commented on CXF-1396:
---------------------------------------
I'm leaving this assigned to Dain, but really it's a deeper Aegis issue that
requires more thought.
The combination of Aegis+JAX-WS ignored @WebParam until Dain turned it on.
However, the naming that parameter has the effect of causing Aegis to name a
global XML Schema type after it. This prevents two params from sharing the same
name.
If we want JAX-WS to be compliant when running with Aegis, we can't be
preventing duplicate parameter names across methods.
So we need to change something: less schema types, or in a pinch more unique
schema types.
> 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.
