Mailing-List: contact java-user-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@axis.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=6owrYnpsQNEgxj/2aT+EB0PH4fuI9LnwEsACyfwjqOiPqXSyE7N2YMIwlrx7I5oOUSG1YIrViOy1p+lLZMqsKSP/TXtFj9iWeH5PbWefQJHiwK6pb71/JBNmg5xvyqpBB09q3Wh68mF+YUJZK4WLnCFQDVebrVkyCsN91DjzUBA=;
Message-ID: <193706.24643.qm@web45502.mail.sp1.yahoo.com>
References: <485946.67008.qm@web45511.mail.sp1.yahoo.com>
 <AANLkTinGtXDEcDh9kmhSqzXLkLMtL5p9PzDL4iCTjYmR@mail.gmail.com>
Date: Sun, 23 Jan 2011 04:11:50 -0800 (PST)
From: am am <akmeref@yahoo.com>
Subject: axis2 session scopes
To: java-user@axis.apache.org
In-Reply-To: <AANLkTinGtXDEcDh9kmhSqzXLkLMtL5p9PzDL4iCTjYmR@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-228202929-1295784710=:24643"

--0-228202929-1295784710=:24643
Content-Type: text/plain; charset=us-ascii

I am starting on axis2 (1.5.4).
I am looking into the various session scopes for web services (request, 
soapsession etc).
By experimenting, I notice that in all scopes except the application scope, 
there is a new instance of my web service being created per service call.
Only by setting the scope to "application" in the services.xml, the web service 
is instantiated only once, and being re-used across all web service calls.
My testing for this, was actually a print statement in the web service 
constructor. The constructor was called for scope="request" or 
scope="soapsession" or scope="transportsession" for each ws call.
So my question is the following: Is this the case in axis2? And if yes, for 
non-trivial web services, isn't it very costly (to re-instantiate per service 
call)?
Is the recommended approach to use application scope services? Or my 
understanding is wrong here?

Thank you!


--0-228202929-1295784710=:24643
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">I am starting on axis2 (1.5.4).<br>I am looking into the various session scopes for web services (request, soapsession etc).<br>By experimenting, I notice that in all scopes except the application scope, there is a new instance of my web service being created per service call.<br>Only by setting the scope to "application" in the services.xml, the web service is instantiated only once, and being re-used across all web service calls.<br>My testing for this, was actually a print statement in the web service constructor. The constructor was called for scope="request" or scope="soapsession" or scope="transportsession" for each ws call.<br>So my question is the following: Is this the case in axis2? And if yes, for non-trivial web services, isn't it very costly (to re-instantiate per service call)?<br>Is
 the recommended approach to use application scope services? Or my understanding is wrong here?<br><br>Thank you!<br><br><br><br> </div><br>

      </body></html>
--0-228202929-1295784710=:24643--