[jbossts-issues] [JBoss JIRA] Closed: (JBTM-502) XTS code is relying upon JBowssWS Native W3CEndpointReference feature which disappears in JBossWS 3.1.0

Andrew Dinn (JIRA) jira-events at lists.jboss.org
Tue Mar 3 12:24:22 EST 2009


     [ https://jira.jboss.org/jira/browse/JBTM-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Dinn closed JBTM-502.
----------------------------

    Resolution: Done


Fixed by r25483. Now uses the same horrible transformation via an XML representation employed by Glassfish and JBossWS.


> XTS code is  relying upon JBowssWS Native W3CEndpointReference feature which disappears in JBossWS 3.1.0
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-502
>                 URL: https://jira.jboss.org/jira/browse/JBTM-502
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: WS-T Implementation
>    Affects Versions: 4.5
>            Reporter: Andrew Dinn
>            Assignee: Andrew Dinn
>             Fix For: 4.6
>
>
> The XTS code relies upon method getAddress() of class W3CEndpointReference in the JBowssWS Native stack implementation. This method has been removed in JBowssWS Native 3.1.0 because the implemenation does not pass the TCK tests if it is included. So, the XTS code needs to identify another means of obtaining the address wrapped up inside a W3CEndpointReference.

-- 
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

        



More information about the jbossts-issues mailing list