Tony, Is there a JIRA opened for the bug? If not, can you open one?
Nadir Amra Tony Dean <[EMAIL PROTECTED]> wrote on 08/05/2008 04:27:37 PM: > Hi, > > I have my service scope set to "application" even though my service > is stateless. That is, I do not store any session information with > my service. My thinking was by loading only one instance of my > implementation class (not reloading on every request which is the > case for "request" scope), it would perform better. > > However, there is a bug in Axis2 such that serviceGroupContext > (serviceContext) are never purged from the ConfigurationContext when > a service is removed. Therefore, if a new service by the same name > is later added it will be associated with the old implementation > class. The only way to remedy this situation is to restart Axis2 > and/or the server. > > So, I'm wondering if am I gaining that much of a performance boost > by using "application" scope? Please advise. > > Thank you. > > Tony Dean > SAS Institute Inc. > 919.531.6704 > [EMAIL PROTECTED] > > SAS... The Power to Know > http://www.sas.com > > > > --------------------------------------------------------------------- > 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]
