SOAP Monitor: not just forwarding messages ?

http://maul:8080/jaxws-jaxws_stateful_s ... ookstoreHi,

I am using soapUI 3.5 on Linux/x86.

I am working on METRO 2.0 's stateful sample (with the server deployed on Glassfish), and I am using the SOAP Monitor to capture the message exchanges between the client and the server. My intent is to experiment soapUI features as regards recording and replay (generation of tests and MockServices).

However, It seems that SOAP Monitor only shows me part of the messages... and the client may even crash !

The only thing I have changed in the sample is edit the client source (Main.java) to change dynamically the port number in the endpoint address for the bookstore port. The aim is to set it to SOAP Monitor listening port.

Apparently, the deployed servlet processes requests on 2 different URIs:
'classical' stateless WS: http://maul:8080/jaxws-stateful/bookstore
stateful WS with WS-A enabled: http://maul:8080/jaxws-stateful/book

Therefore, I have added the two associated WSDL to my soapUI project.

The difficulty is which URI to choose to set the SOAP monitor's "endpoint for HTTP Tunnel":
o http://maul:8080/jaxws-stateful/bookstore : the client seems to be running, but lots of messages are lost
o http://maul:8080/jaxws-stateful/book : the client crashes, with a problem to dispatch a request on the server side

It seems SOAP Monitor (in HTTP Tunnel) is not simply forwarding messages, as TcpMon does... but is editing their contents.

Thanks for any hint on how to proceed to have the sample work, and all messages captured by SOAP Monitor.

Regs,
JC.