[
https://jira.jboss.org/browse/JBTM-755?page=com.atlassian.jira.plugin.sys...
]
Andrew Dinn closed JBTM-755.
----------------------------
Resolution: Done
The current unit tests and interop tests now work on current AS trunk/WS-CXF and AS
6.0.0.M3/WS-Native.
Fixing this necessitated tweaking the OASIS standard WS-T WSDL so that the WS-T services
accept incoming soap faults. This is the only way that it is possible for the WS-T
services to use JaxWS to dispatch a Soap Fault to a client configured W3C endpoint which
also has to be used to dispatch a conventional WS-T protocol JaxWS request. Now that the
CXF endpoints include metadata identifying the service and port there is no way to
dispatch a request which is not identified in the service WSDL.
This has required modifying the SEI implementation beans to provide corrresponding
@WebMethod annotated methods to handle these incoming faults. It has also required
dropping the independent SoapFaultService client and WSDL which was previously used to
dispatch faults using JaxWS. This service has been retained in the interop test code where
there is no need to use W3C endpoints to dispatch faults.
Fix various problems caused/found by latest CXF build
-----------------------------------------------------
Key: JBTM-755
URL:
https://jira.jboss.org/browse/JBTM-755
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.11.0
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.12.0
Various things have either been broken by or shown to be already broken by the latest CXF
build. This JIRA is a catch all for them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira