There is no requirement for two code generators to generate identicle code as
the JAX-RPC mapping file is used to describe how the schema was mapped to Java.
If you have a reproducable scenario where invalid code is being generated
please raise a bug in Jira with the required files to reproduce
Once again the root cause of the problems are the JBossWS tools used to
generate the required artifacts.
For comparison I used XFire (=open source Java SOAP framework).
I got a total of X artifacts generated using JBossWS wbservices stack and
related tools.
In comparison I got a total of (X+10)
OK this is what I discovered:
The Could not update IN parameter to be INOUT... error comes from
processOutputDocElement method inside JAXRPCMetaDataBuilder class. The
processOutputDocElement is called from
anonymous wrote :
| buildParameterMetaDataDoc(OperationMetaData opMetaData,
