Hi Andreas;
In 0.94 release we improved our session and scope management as we think
right . And there service author can deploy his service in four different
scope
1. Request Scope
2. Transport Scope
3. SOAP Session Scope
4. Application scope
and user can configure the scope by adding scope attribute in his service
element as follows
<service name="foo" scope="application">
then the service instance will be created and stored in the ServiceContext.
And the important thing is that the serviceContext will be stored in
different location depending on scope
1. if it is request scope it wont store
2. if it is Transport scope then it stores in SessionContext
3. If it is SOAP Session scope that it will store in configuration context
and will be time-out after some times if the services does not touch
4. If the scope is application then the servicecontext will store in
configuration context and it will there forever (until server shutdown)
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Andreas Bobek" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, January 13, 2006 5:58 AM
Subject: [Axis2-0.94] application scope for ServiceClass missing
Hi,
in Axis2 0.93 follow configuration in a services.xml was possible:
<parameter name="ServiceClass" locked="false">com.MyService</parameter>
<parameter name="scope">application</parameter>
The AbstractMessageReceiver class in Axis2 0.94 takes no care about the
scope parameter anymore.
How can I force Axis to create only one instance of my service
implementation class for the whole runtime?
Thanks and good night,
Andreas Bobek.
---------------------
http://www.andreas-bobek.de
http://www-md.e-technik.uni-rostock.de/~ab113/index.html
