Hi Deepal And what impact can / will it have in regard to
a) state fule sessions, b) each of the 4 possible session scopes a service can run in, if Axis2 client side stubs/API-routines are not thread safe? Can you please explain this a bit further or point us to documentation? Are only generated client side stubs not thread safe OR are underlaying client side API routines not thread safe either? AND are server side generated skeletons thread safe? can you explain or doucment us about AXIS2 thread safety in general? Client side API's are used to build client example code. This has lead to my JIRA-1991 reported side effects which makes client#1 thread fail with invalidServiceGroupContextID just after client#2 thread starts calling a MyService in scope=soapsesion. Regarding thread safety : Is the underlaying object model up on which Axis2 is implemented and hence - services are built - thread safe implemented? I would like to know the "boundaries" in therms of classes/objects which are regarde thread safe and intermediate classes/objects which are regarded not thread safe. How was thread safety tested to confirm that Axis2 is thread safe? I am asking all this because I have to implement state full sessions, sessions where each client thread hits its unique (UUID) own instance a of service providing server side object. Josef Stadelmann -----Ursprüngliche Nachricht----- Von: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 08:05 An: [email protected] Betreff: Re: thread safe? Hi Michael ; Nope , Axis2 client side is not thread safe. Thanks Deepal > Can anyone confirm whether the stub Axis2 generates is thread safe of > not? > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
