Hi Paramdeep, If all you're concerned about is Axis and MS-SOAP I think that headers are a good approach. This is probably the best way of handling sessions in the long run, but until there's a standard I don't expect to see it supported widely enough to be generally useful. My point with the approach I suggested is that it provides session support now for any SOAP implementations that can intercommunicate at all.
- Dennis Paramdeep Singh wrote: >Hi, > >MS-SOAP supports sessions using SOAP headers. There is a sample included >with the standard examples install. > >I think that Apache SOAP 2.2 doesnt have a support for SOAP headers. But it >seems that Apache AXIS (The new rewrite version of Apache SOAP) does have a >support for SOAP headers. > >I havent tried using it, but have seen posts, from which it appears that >AXIS has that support! > >Warm Regards, >Paramdeep > >----- Original Message ----- >From: "Dennis Sosnoski" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Thursday, April 04, 2002 2:00 AM >Subject: Re: HTTP redirects and SOAP > > >>The only way I know of to provide session support that works across all >>platforms is to basically implement it yourself. Build a wrapper for >>your statefull session EJB (or whatever other session-based class you >>want to use), adding a call to the wrapper that gets a session >>identifier like: "String getSession(String user, String password)" (user >>and password are optional, depending on your application). The wrapper >>needs to get an instance of the session-based class when this call is >>executed, and return a unique identifier mapped to that instance in a >>HashMap or equivalent. >> >>For each method you want to make available in the session-based class, >>add a new parameter "String id" to the corresponding method in the >>wrapper. The wrapper can use this to look up the instance of the >>session-based class associated with that identifier, then call the >>wrapped method on that instance. >> >>Depending on your requirements you may also want to add a call >>"endSession(String id)", and may also want to use timeouts for the >>session-based class instance (so that if the session is not used for >>some period of time it gets dropped). >> >>Kind of ugly and tedious, but it's the only sure way of doing sessions >>that I know of. Anybody have a better approach? >> >> - Dennis >> >>Dennis M. Sosnoski >>Sosnoski Software Solutions, Inc. >>http://www.sosnoski.com >>
