[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2528) Missing parameterOrder in portType/operation
[
https://jira.jboss.org/jira/browse/JBWS-2528?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBWS-2528:
---------------------------------------
This is connected to this too: https://issues.apache.org/jira/browse/CXF-2138
The reason is the fix for CXF-2110 takes care of RPC style endpoints only, while this also
affects DOC/LIT endpoints (see. com/sun/ts/tests/jws/webparam/webparam1 that was
previously failing in being configured because of JBWS-2529)
Missing parameterOrder in portType/operation
--------------------------------------------
Key: JBWS-2528
URL: https://jira.jboss.org/jira/browse/JBWS-2528
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-3.1.1
The cxf java2wsdl seems to fail in generating the wsdl portType/operation element in some
cases where soapHeader and IN/OUT parameters are used at the same time. This was revealed
by the webparam3 reverse test configuration in the jws tck5 module.
In that case we have
<wsdl:portType name="webParam3WebService">
<wsdl:operation name="hello3">
<wsdl:input name="hello3" message="tns:hello3">
</wsdl:input>
...
instead of
<wsdl:portType name="webParam3WebService">
<wsdl:operation name="hello3" parameterOrder="id Name
Employee">
<wsdl:input name="hello3" message="tns:hello3">
</wsdl:input>
...
We should first reproduce this in a test case in our testsuite, then understand if this
is actually a cxf issue or an integration one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira