Thank you Bobby. So other than application level solution, will jaxrpc plan to have build-in
support like this in the future? that way the handlers written will be a lot more portable across
different jaxrpc implementations. For instance, in axis, one can obtain an AxisEngine object from
the messageContext which available cross calls.
Nan
> -----Original Message-----
> From: Bobby Bissett [mailto:robert.bissett_at_sun.com]
> Sent: Tuesday, October 21, 2003 10:09 AM
> To: users_at_jax-rpc.dev.java.net
> Subject: Re: MessageContext->Stub and Stub->MessageContext?
>
>
> >
> > handleResponse(mc) call for the first service call will
> retrieve the id/token from soap header
> > and would like to save it "somewhere" on the client, then
> handleRequest(ms) call for the next
> > service call will add id/token back to the soap header. my
> question is where is "somewhere"
> > in a standard jaxrpc implementation????
>
> One easy way to have a handler and client share information
> is to use a
> singleton holder class. Since the handler and client are in
> the same vm,
> the handler can do something like:
>
> MyHolder.getInstance().storeData(String myID);
>
> ...and the client can retrieve it, as can the handler again
> for the next
> request.
>
> Cheers,
> Bobby
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net