[
https://issues.apache.org/jira/browse/CXF-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies reassigned CXF-1396:
-------------------------------------
Assignee: Dain Sundstrom (was: Benson Margulies)
Dain,
The problem here is that you did something with the JAXWS @WebParam that has,
ahem, surprising effects that I think are wrong. @WebParam(name = "foo")
assigned the name "foo" to a complexType. Now, two params in the same schema
can't have the same name.
Now, it occurs to me that Aegis hypothetically worked with JAX-WS all along, so
perhaps I'm tagging you with this unfairly, and someone else did it.
> Aegis and java2ws results in strange schema errors
> --------------------------------------------------
>
> 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.
