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
Erik,
That's exactly how it should work - the beauty of IoC! :)
Do you have the IoC filters / listeners installed? You need these to be
plugged in for the IoC system to work.
http://wiki.opensymphony.com/space/WebWork+2+Components
But what you're doing is how it should be done!
M
On 2/7/03 12
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
On Tuesday, July 1, 2003, at 11:07 PM, Jason Carreira wrote:
Did you put the Interceptor in your interceptor stack to set up the
components? It looks like this:
class="com.opensymphony.xwork.interceptor.component.ComponentIntercepto
r
"/>
doh! sorry for the boneheaded mistake on that one.
yup,
10:33 PM
> To: [EMAIL PROTECTED]
> Subject: [OS-webwork] application scope
>
>
> On Tuesday, July 1, 2003, at 04:52 PM, Jason Carreira wrote:
> > Check out ServletActionContext.getServletContext(). This should let
> > you do what you want to do (at the expense of not b
On Tuesday, July 1, 2003, at 04:52 PM, Jason Carreira wrote:
Check out ServletActionContext.getServletContext(). This should let you
do what you want to do (at the expense of not being able to use your
Action outside a Servlet container, but you're used to Struts, so we
forgive you :-))
I have thi