Hi Samisa
Samisa tell me why we have a routine which is able to set / get
session scope if it is not used by any code? Where is it used?
May I just overlook something.
Where I talk about scope="soapsession" support in Axis2/C
I mean that Axis2/C should be able to read from service.xml
this attribute and then act acordingly. AFAIK this is not the
case. .. to read and behave about like Axis2/Java
I do not say, "we can not use WS username tokens". However we need
the following relations anyway.
1 PC : 1 session with Axis2(Java/C) talks to 1 OpenVMS Process
1 PC : 2 sessions with Axis2(Java/C) talks to 2 OpenVMS Processes
2 PC : 2 sessions with Axis2(Java/C) talks to 2 OpenVMs Processes
2 PC : 2 sessions with Axis2(Java/C) talks to 4 OpenVMs Processes
you get it.
We need this not only for security reasons but our legacy code base
about 90'000 Lines of Pascal Code is now about 25 years old and runs
since ever on a per process base, and it is by far not threadsafe!
Too many variables are shared via globals among functions and we
use shared memory for inter process communication. We are not going
to change that on this legacy server. Hence we need to support our
relations as given above. It works at our site with CORBA until now
and we are just goibng to replace our CORBA backbone by a new
WebService backbone.
And Axis2 Java supports the various scopes but Axis2/C today not.
Thank you for your help
Josef.Stadelmann@
axa-winterthur.ch
-----Ursprüngliche Nachricht-----
Von: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 5. Dezember 2007 05:07
An: Apache AXIS C User List
Betreff: Re: AW: AXIS2/C and scope="soapsession"
Stadelmann Josef wrote:
> Hi Subra,
>
> The problem you see tells me that it is more wors with Axis2/C in
> regard to sessions
> as I expected.
>
> When looking at what I said below, regarding the defines made in
> axis_config.h
> one can get the impression that sessions are somewhat handled, but
> when I read
> your e-mail the I get a different feeling and the idea that some
> work is pending on Axis2/C
SOAP session is not tested, even though the code may be there. All that
is supported is demonstrated in the sg_math sample.
>
> Meanwhil I am switching over from Axis2/C the simple_httop_server
> to Axis2 Java and call
> from a service object per session, an real instance of the class,
> one per soap session, via a
> WSIT toolkit through JVM my legacy services written in C,
>
> and there, in this legacy C code, I use my axiom and axutil libs
> ported to OpenVMS, from
> my wrapper of the legacy service.
>
> That way I can at least say: I have scope=soapsession supported by
> Axis2 Java and get to a
> OpenVMS process after all, one for each client calling in,
> through my webservice in Java.
>
> my issue is: one session to one OpenVMS process for authentication
> purpose.
>
If it is about authentication, why not use WS-Security UsernameToken?
You can use this with the Rampart/C module and is the right way to do
auth in Web services.
Samisa...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
