Hello,
is it
possible to create a soa-rpc-request message, save it, but don't send
it?
I
would think of this being useful if I want to split up my total processing into
several, controlable steps. That is, have the ability to not execute a step, but
only generate the requestmessage for the next processing step. Save the message,
and then manually insert the generated request into the next step. Great for
error tracking and tracing functionality.
Is it
possible? How would I do it?
The
lowest level client operations does something like:
String endpoint =
9 "http://nagoya.apache.org:5049/axis/services/echo";
10
11 Service service = new Service();
12 Call call = (Call) service.createCall();
13
14 call.setTargetEndpointAddress( new java.net.URL(endpoint) );
15 call.setOperationName(new QName("http://soapinterop.org/", "echoString"));
16
17 String ret = (String) call.invoke( new Object[] { "Hello!" } );
18
9 "http://nagoya.apache.org:5049/axis/services/echo";
10
11 Service service = new Service();
12 Call call = (Call) service.createCall();
13
14 call.setTargetEndpointAddress( new java.net.URL(endpoint) );
15 call.setOperationName(new QName("http://soapinterop.org/", "echoString"));
16
17 String ret = (String) call.invoke( new Object[] { "Hello!" } );
18
Line
17 invokes the service. Which I sometimes don't want. But also at that moment it
will create a xml-soap message and send it over the wire. I would only like to
create the message, and then get a handle to it so that I can save it. Would
this be possible?
Regards, Jan.
