Anders,

This is what I had thought would be a good solution for the sitemesh problem. Use taglibs to get the valuestack from the request.

There also seem to be problem with trying to access the value stack inside sitemesh. What about multiple sitemesh pages (using page:applyDecorator). You can even do a page:applyDecorator inside a decorator. How would this work with sitemesh? Which valuestack do you want?

If you used a filter, then this would work in Orion & Resin, but Tomcat & Jetty which only apply filters once per top-level request, this would completely break.

Even if your decorator itself was an action (which admittedly isn't often, but it could happen), how would this value stack work?

It doesn't sit right to me.

Cheers,
Scott

Anders Engström wrote:
Hi,

a recent thread discussed WW2 and Sitemesh. I've got some
questions/thoughts on WW1.3 and Sitemesh.

In ServletDispatcher the current ActionContext (and ValueStack) is
removed from the request when the view have been rendered. But, the last
action is put in the request with the name ServletDispatcher.STACK_HEAD.
No where else in the code is this feature used.


What was the initial motivation to put the last executed action in the
request?

After seeing this I thought that perhaps the taglibs would use this as a
"last resort" when looking up properties - but this is not the case.

//Anders




--


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

Reply via email to