[EMAIL PROTECTED] wrote:
The settup you want is the normal way for stateful session beans to work. A reference to the stateful session remote interface for each client will resolve to the original instance. thus, statefull session beans serve a single client as opposed to stateless session beans which are served up by the container from a pool on each request.Thank you for answering so quickly and so efficiently, it's exactly what I was looking for!!!
If you set the scope to session rather than application you should be fine and it will only call the constructor to create the bean once for each thread.
Regards
Steve
Now, I can manage multiple clients with no problem.
Just two precisions (maybe I'm wrong but I've constated that): 1- Each client must use only one Service for each call they make 2- For each created call, the following line must be added : call = (Call) globalService.createCall(); call.setMaintainSession(true);
Doing that, everything works well!
I've got one other question :
I'm using the 1.2alpha version of axis and I tried to use streaming in order to get better performances.
Modifying the wsdl file doesn't implied errors but the API I'm currently using don't propose the setStreaming(boolean) for the Call object.
When will the cvs version that contains the new functionnality will be released?
Thank you for your help
Cheers karim
