[
https://issues.jboss.org/browse/WFLY-2201?page=com.atlassian.jira.plugin....
]
Gytis Trikleris moved JBTM-1940 to WFLY-2201:
---------------------------------------------
Project: WildFly (was: JBoss Transaction Manager)
Key: WFLY-2201 (was: JBTM-1940)
Component/s: XTS
(was: XTS)
(was: TXFramework)
Security: (was: Public)
Fix Version/s: 8.0.0.Beta1
(was: 5.0.0.Final)
Server-side XTS handlers not added if @WebService#portName is
missing
---------------------------------------------------------------------
Key: WFLY-2201
URL:
https://issues.jboss.org/browse/WFLY-2201
Project: WildFly
Issue Type: Bug
Components: XTS
Reporter: Paul Robinson
Assignee: Gytis Trikleris
Priority: Minor
Fix For: 8.0.0.Beta1
To reproduce, remove portName or targetNameSpace attributes from
org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework
suite. You will see that the test fails with:
{code}
"MustUnderstand headers:
[{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not
understood"
{code}
The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a
valid @WebService annotation if these attributes are missing. In reality they are optional
and an application should be allowed to leave them off. However, these attribute values
are used by the XTS subsytem, so we would need to find a way of using the defaults if they
are missing from the annotation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira