I think it's #params['home'] > -----Original Message----- > From: Frederick N. Brier [mailto:[EMAIL PROTECTED] > Sent: Monday, October 06, 2003 3:07 AM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] Using the PushTag > > > That seems like a pretty cool idea. And the filter could > null out the > ActionContext ThreadLocal on exit allowing it to be garbage > collected and > not hanging around. BTW, what is the syntax for accessing a request > parameter off of the value stack? Is it "$req.home"? > Assuming home is the > key of the ServletRequest attribute. Would having the ActionContext > initialized in a Filter simplify the Webwork2 design if it > was all done in > one place? Thank you again. > > Fred. > > At 10:14 AM 10/5/2003, you wrote: > >I don't know how we can get this to work... The > ActionContext with an > >empty ValueStack will be created as a default ThreadLocal if > it doesn't > >exist when you go to access it, but to access things like > the request, > >it needs to be set into the ActionContext at some entry > point, like the > >ServletDispatcher or ActionTag. > > > >If you're interested in accessing these types of things, I would > >suggest creating a Filter which sets the request, response, session, > >etc into the ActionContext... > > > >Jason > > > > > -----Original Message----- > > > From: Frederick N. Brier [mailto:[EMAIL PROTECTED] > > > Sent: Friday, October 03, 2003 9:17 PM > > > To: [EMAIL PROTECTED] > > > Subject: [OS-webwork] Using the PushTag > > > > > > > > > I cannot find an example the syntax to pass as the value > attribute > > > of the <ww:push> tag to retrieve an attribute from the > > > HttpServletRequest. Further, it looks as if the PushTag calls the > > > ActionContext to retrieve the valueStack. According to my > > > debugger, the > > > stack is empty. Can the PushTag be used from a Sitemesh > > > Decorator since it > > > is not within the execution of an Action? I cannot follow > > > where in the > > > code a translation of "$req.home" would become a lookup of > > > the request > > > attribute "home". I do see where the ActionTag put(s) > > > multiple values in a > > > context map in createExtraContext(), but do not understand how it > > > works. Thank you. > > > > > > Fred. > > > > > > At 06:41 PM 10/3/2003, you wrote: > > > >I will try the push tag. Thank you again. BTW, would it be > > > silly to > > > >have > > > >a filter that does nothing but clear the ActionContext > > > ThreadLocal variable? > > > > > > > >Fred. > > > > > > > >At 09:16 AM 9/30/2003, you wrote: > > > >>What are you trying to do in your decorators? If you access > > > things in > > > >>the > > > >>request, where the Action will be bound with its id, you > > > can push this > > > >>action onto the ValueStack using the ww:push tag and use > > > all of the other > > > >>tags as normal. > > > >> > > > >>I don't think we're going to make the ActionTag leave its > > > >>ActionContext out there. It needs to be returned to the > original. > > > >> > > > >> > -----Original Message----- > > > >> > From: Frederick N. Brier [mailto:[EMAIL PROTECTED] > > > >> > Sent: Monday, September 29, 2003 10:20 PM > > > >> > To: [EMAIL PROTECTED] > > > >> > Subject: Re: [OS-webwork] WW2 Tags in SiteMesh decorators > > > >> > > > > >> > > > > >> > This is exactly what I got working this weekend with my > > > change to > > > >> > the <ww:action> tag. I am using Webwork2 with SItemesh. > > > My Action > > > >> > class is populated via the interceptors and an IoC component > > > >> > and populates the header.jsp referenced in my Sitemesh > > > >> > decorator default.jsp with a <ww:property> from the Action. > > > >> > > > > >> > The reason it didn't work originally was the "ActionTag > > > wipes out > > > >> > own ActionContext" issue, now in Jira. > > > >> > > > > >> > Fred. > > > > > > > > > > > > > > > >------------------------------------------------------- > > > >This sf.net email is sponsored by:ThinkGeek > > > >Welcome to geek heaven. > > > >http://thinkgeek.com/sf > > > _______________________________________________ > > > >Opensymphony-webwork mailing list > > > >[EMAIL PROTECTED] > > > >https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Opensymphony-webwork mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > > > >------------------------------------------------------- > >This sf.net email is sponsored by:ThinkGeek > >Welcome to geek heaven. > >http://thinkgeek.com/sf > _______________________________________________ > >Opensymphony-webwork mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
