Re: [OS-webwork] application scope

[Erik Hatcher]

Matt - thanks.  That, of course, did the trick.  I had stumbled on this 
stuff and was close to discovering it myself.  What I wanted to try to 
avoid was constructing the AppConfig object itself.  I presume this 
would be done by getting the one the component manager created by 
making my servlet AppConfigAware and doing:

	 container.initializeObject(this);

I think Mike mentioned something like this in his WW2 presentation 
even.  Am I on track?

Either way, it works as I want it to with this bit of trivia and 
constructing a second instance of the object and replacing it is no big 
deal.

	Erik

On Wednesday, July 2, 2003, at 05:24  AM, Matt Ho wrote:
I assuming since this is during your servlet's init method, you want 
access to components with an application lifespan.  The following code 
grabs the component manager for application lifecycle objects and 
tells it to populate the instance of MyObject with all the appropriate 
components.

public void init(ServletConfig config) {
ServletContext application = servletConfig.getServletContext();
ComponentManager container = 
(ComponentManager)application.getAttribute("DefaultComponentManager");

MyObject foo = new MyObject();
container.initializeObject(foo);
}


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork