Re: Completion of ACTION-255

Hi Eric,

I don't think so....  Two errors were simple defects, related to target
service which should be picked up by tests that do not specify
targetService (e.g. test008) and tests that do specify targetService (e.g.
test0002).  These were fixed by the following APAR :
WSA:ReplyTo response acts like a request and required "targetService"
property which should not be require

The other error was a problem related to the precedence of WS-Addressing
headers, which wouldn't be covered by our tests.  This problem was fixed in
this APAR:
PM23372: WSA:FaultTo is not honored when JMSReplyTo is present

Regards
Mark



From:	Eric Johnson <eric@tibco.com>
To:	Mark Phillips/UK/IBM@IBMGB
Cc:	<public-soap-jms@w3.org>
Date:	18/10/2011 14:01
Subject:	Re: Completion of ACTION-255
Sent by:	public-soap-jms-request@w3.org



Hi Mark,

Thanks for the report.

Along the way, were there any issues identified that should be added to
our test cases?

-Eric.

On 10/18/11 2:48 PM, Mark Phillips wrote:
> To complete ACTION-255 [1] I have documented my findings below on the
> testing conducted between the two different IBM products - WebSphere
> Message Broker (WMB) and WebSphere Application Server (WAS).
>
> Both these products have SOAP/JMS capabilities and both products use Axis
2
> for underlying SOAP support, but the SOAP/JMS implementation in each
> product is different.  Each SOAP/JMS handler was developed independently
> from the other.
>
> Interoperability testing has been carried out between WebSphere Message
> Broker 7.0.2 and WebSphere Application Server 7.0.9 and the tests found a
> number of defects which have been fixed in subsequent maintenance levels.
> The products now pass their interoperability tests, and so have been
> demonstrated to be interoperable.
>
> Regards
> Mark
>
> [1] http://www.w3.org/2002/ws/soapjms/tracker/actions/255
>
>

Received on Monday, 24 October 2011 22:20:39 UTC