[
https://jira.jboss.org/browse/JBTM-749?page=com.atlassian.jira.plugin.sys...
]
Andrew Dinn closed JBTM-749.
----------------------------
Resolution: Done
resolved by removing action attribute and by not relying on annotations rather than wsdl
on the server side. client side wsdl is still used because native fails without it.
WSTX WSDL should not be using wsa:Action attribute
--------------------------------------------------
Key: JBTM-749
URL:
https://jira.jboss.org/browse/JBTM-749
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
The switch over to CXF as the default stack in AS 6 has exposed a problem with the WSTX
WSDL files. XTS currently employs the 1.1 WSDL as originally published by OASIS. This WSDL
includes wsa:Action attributes in the port type declarations. This causes a problem on CXF
2.2.8 where the Message Addressing Properties (MAP) handler fails to locate the Action
attribute installed in response messages -- it does nto check for the 2005/08 wsa space --
and, consequently, runs into a null pointer exception.
The OASIS 1.1. WSDL has been republished (somewhat sneakily) without the Action
attributes. This later version should be used. Instead of relying on the wsa:Action
attribute the server endpoint implementation classes should employ @Action attributes on
the implementation methods to define the input and output Actions associated with the web
methods.
--
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