[
https://jira.jboss.org/jira/browse/JBTM-689?page=com.atlassian.jira.plugi...
]
Andrew Dinn commented on JBTM-689:
----------------------------------
I have fixed by adding @javax.xml.ws.Action annotations to the service endpoint
implementation classes and tested it in the latest JBossAS trunk with a JBossWS Native
stack and it works. I have not yet tried this for the CXF version but in theory it ought
to work. However, it is maybe not so simple. The withdrawn JAX-WSA spec specified that
annotation @javax.xml.ws.addressing.Action should be used for this purpose. JBossWS
defines but does not employ this annotation. I don't think anything else specifies
that the first of these annotations should be used to define the WSA attribute. So, who
knows what is right and what CXF will do. Anyway, working on the Native stack is better
than not working at all and, if we are lucky, it might also work on CXF. So we will call
this a wrap.
Register response interop issue
-------------------------------
Key: JBTM-689
URL:
https://jira.jboss.org/jira/browse/JBTM-689
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.7.0
Environment: JDK 5 update 21, JBoss AS 5.1.0 GA, JBoss Web Services - Native
3.1.2 GA, JBoss Transactions 4.7 GA, Windows XP
Reporter: Guzm?n Llamb?as
Assignee: Andrew Dinn
Wrong registerResponse action message breaks interoperability. See
http://community.jboss.org/message/522118#522118 for more details
--
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