[
https://jira.jboss.org/jira/browse/JBESB-3035?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3035:
-------------------------------------
The following comments have been added to the SOA issue.
Tom Fennelly - 16/Dec/09 06:04 AM To me, this looks to be an issue with JBossWS. The
webserive operation itself is not honoring the @Oneway annotation on th webmethod. The WS
container is returning the exception as thrown by the webmethod.
Tom Fennelly - 16/Dec/09 06:10 AM I'll look at the SOAPProxy code and see is there a
way we can enforce this from inside the ESB.
Kevin Conner - 16/Dec/09 06:13 AM The SOAP Proxy should be doing just that, proxying the
response (whatever it is). If this is a JBossWS issue then we need to pass it over to
them,
A one-way message that throws exception should not return HTTP code
500
-----------------------------------------------------------------------
Key: JBESB-3035
URL:
https://jira.jboss.org/jira/browse/JBESB-3035
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Kevin Conner
Assignee: Tom Fennelly
Fix For: 4.7 CP1
--
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