|
I’ll try to help you. I did not reply to your first post,
because it is unclear if you are talking about a communication that multiplexes
multiple sessions across a single server to server link. In that use case, a cookie based session
id just won’t work. It would
be analogous to two separate end-users using a single browser to connect to a web
application. The session
information is identical and you need to rely on a token passed in the
soap:header or as a method parameter; not the built-in AxisSession that relies
on HTTP cookies. The current
session information is appropriate for webapp style session handling across clients
that don’t thread conversations. In a threaded, multi-conversation scenario,
one has to currently hand-code a session token to pass with the requests. A handler is just a pre-processor before
the request reaches the service code.
Handlers are commonly used for filtering, logging, authentication,
authorization, and yes, augmenting the request object with session specific
information. From an Axis implementation perspective,
the handler would read the session key passed by the client (in an HTTP header
or SOAP envelope parameter), and pull up the session state information. The session information could be
attached to the MessageContext object that is passed to every processing object
in the chain (including the service handler). Hope this helps…. /Chris -----Original Message----- I had been looking for a solution on how to implement
session's in a scenario where the client will be in asp (i.e. Microsoft Toolkit
2.0 which doesn't support cookie's) and services on Apache Soap (i.e. Axis).
Plenty of answers in the forum keep telling that we could use Handlers or
SimpleSessionHandler to do the same however couldn't find a one small
implementation example. Can any one help me by providing a simple example for
the same. Thanks Srinivas Do You
Yahoo!? |
- Can any one help me with this please :(( :(( Srinivas Reddy
- Chris Haddad
