I hope you guys can get this out for 2.0 release because im using includes right now it is sucks! (dieing to use sitemesh..) :)

Pat Lightbody wrote:

Mike Cannon-Brookes has suggested that we have a filter to do the cleanup as
well. I think it's a very scary idea myself :)

I don't think that this is much of an issue at this point. As long as we
keep a reference of the value stack in the HttpServletRequest and change the
tags to use that than SiteMesh will work fine without any trickery with
filters or cleanup.

-Pat

----- Original Message ----- From: "Jason Carreira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 04, 2003 11:01 PM
Subject: RE: [OS-webwork] WW2 Tags in SiteMesh decorators



I don't know... Have you had problems with it?



-----Original Message-----
From: Frederick N. Brier [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 6:41 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] WW2 Tags in SiteMesh decorators


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

Reply via email to