Components in XWork's IoC container are constructed lazily -- so yes, an
ActionContext should exist. Configuration is looked up from the classpath --
you'll need to override the ApplicationLifecycleListener to change that.
-Pat
----- Original Message -----
From: "Cameron Braid" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 17, 2003 7:33 AM
Subject: [OS-webwork] Xwork Components in WebWork2
> I want to use an IoC approach within webwork2 to provide my manager
> components to my actions.
>
> I have created the managers and enablers, now the problem is - how do I
> configure my manager components ?
>
> I need to be able to work out a path relative to /WEB-INF
> I want to have a config file, either a properties file, or in web.xml to
> allow me to spefity this path.
> Then I was going to get the value of request.getRealPath("/WEB-INF/" +
> path), and set it onto my manager component.
>
> Also, when are application scoped components constructed ? when they are
> first needed, or on initialization of the component manager ?
>
> I need to know this to determine if an ActionContext will always be
> availible when the component is constructed.
>
> Thanks.
>
> Cam
>
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
