I don't think that this should be put into sitemesh at all - it is a *webwork* feature, and sitemesh should not have a dependency on sitemesh at all.
It can easily be done in webwork code, in a way that doesn't affect anyone who chooses not to use it (apart from my email outlining how this won't work with multiple applyDecorator tags).
Cheers, Scott
Chris Miller wrote:
Updating all the taglibs etc to try to find it using STACK_HEAD as a last resort sounds a little messy, and is not required by a large percentage of WW users anyway. The current approach where WW publishes the value so post-webwork code can access it sounds fine. The real problem of course is that the feature isn't documented.
I think the responsibility should be left with Sitemesh to push/pop this value.
--
ATLASSIAN - http://www.atlassian.com Expert J2EE Software, Services and Support ------------------------------------------------------- Need a simple, powerful way to track and manage issues? Try JIRA - http://www.atlassian.com/software/jira
------------------------------------------------------- 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/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
