Stateful services are currently a feature of your SOAP implementation. Most
SOAP implementations don't support them. Those that do use a variety of
mechanisms to reference these services.
Systinet WASP supports stateful services by generating an instance id, which
gets passed as a header element in your SOAP messages. WASP server also
manages the lifecycle of the stateful service, automatically garbage
collecting it when it's no longer being used.
We're working with a few other companies right now to define a standard
header specification to represent stateful services and remote references.
(Tune into the W3C lists for more information.)
NOTE:
WASP doesn't yet support JAX-RPC, although the current API mirrors its
capabilities (compiled stubs, dynamic proxies, and DII clients, type
support, serializers, etc.). We plan to switch over to the JAX-RPC API in
our next release. We already have support for JAXM.
Best regards,
Anne Thomas Manes
CTO, Systinet
> -----Original Message-----
> From: Public discussion on JAX-RPC
> [mailto:JAXRPC-INTEREST_at_JAVA.SUN.COM]On Behalf Of Armond Avanes
> Sent: Saturday, March 09, 2002 3:08 AM
> To: JAXRPC-INTEREST_at_JAVA.SUN.COM
> Subject: Keeping the session at SOAP ?!
>
>
> Hi SOAP Gurus,
>
> I want to know if there is any good and practical
> pattern to keep the session at SOAP calls, other than
> passing a session token everytime as a parameter of
> methods ?!
>
> Any comment ? suggestion ? reference ?
>
> Best Regards,
> Armond
>
> __________________________________________________
> Do You Yahoo!?
> Try FREE Yahoo! Mail - the world's greatest free email!
> http://mail.yahoo.com/
>