[
https://issues.jboss.org/browse/JBWS-3424?page=com.atlassian.jira.plugin....
]
Jim Ma commented on JBWS-3424:
------------------------------
These jar version info is great helpful to reproduce this issue with
jaxws-jboss-httpserver-httpspi. It turns out it's an issue in
jaxws-jboss-httpserver-httpspi-1.0.0.GA and I already fixed it on trunk .
You are right. It's an oneway ws operation , even without wsdl location and it should
return 202.This issue has been resolved in cxf 2.4.5 (please see
https://issues.apache.org/jira/browse/CXF-3926) I got the above wrong response because I
tried it without providing wsdl location in cxf 2.4.4 and with normal jbossweb servlet
transport. In your case, the wsdl location is set in endpoint properties, the oneway
informantion can get from wsdl and does not share this problem. Now it returns the
response as you expected:
---------response------------
>>>> received [HTTP/1.1 202 Accepted]
>>>> received [Transfer-encoding: chunked]
>>>> received [Content-length: 0]
>>>> received [Date: Fri, 03 Feb 2012 08:13:39 GMT]
>>>> received []
>>>> received [0]
>>>> received []
>>>> end.
I attach the patched jaxws-jboss-httpserver-httpspi. Please give a try to verify if it
resolve the switchyard issue. Thanks.
CXF does not return status code 200 when Oneway webservice is invoked
via HTTP
------------------------------------------------------------------------------
Key: JBWS-3424
URL:
https://issues.jboss.org/browse/JBWS-3424
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-4.0
Reporter: Magesh Bojan
Assignee: Jim Ma
Attachments: jaxws-jboss-httpserver-httpspi-1.0.0-SNAPSHOT.jar, reproducer.zip
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira