Glen Daniels wrote:
Yup, I was thinking exactly the same thing. :) The thing is, the other methods all definitively *create* new Context objects - the ServiceGroupContext.getServiceContext() one finds OR creates a ServiceContext (depending on whether there already is one for that service), so "get" actually may be a little more appropriate here. This is one of the reasons I labeled that checkin "part one", and I'd like to continue discussing these relationships in context of the design we want for ServiceContext/ServiceGroupContext and session scoping.
Please don't change any of the scoping logic without serious discussion on the list! I know you've had reservations about the current approach from the beginning but I personally don't agree that something is broken!
Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
