[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensymphony-sitemesh
Subject:    Re: [Opensymphony-sitemesh] sitemesh + ww1 + velocity
From:       Scott Farquhar <scott () atlassian ! com>
Date:       2004-03-31 6:12:54
Message-ID: 20040331001254.B13258 () zeus ! atlassian ! com
[Download RAW message or body]

Jan,

We use a custom servlet dispatcher, which doesn't clean up the action
context, and then a servlet filter that runs after sitemesh.

Alternatively, use content blocks inside the page which you can then
access from the decorator.  This is what we do in Confluence.

Cheers,
Scott

On Wed, Mar 31, 2004 at 02:09:12AM +0200, Jan Berkel wrote:
> Hi,
> 
> I adapted the VelocityDecoratorServlet from CVS to work with Webwork1. It
> will use the velocity config from webwork (basically a cut and paste
> from VelocityHelper).
> 
> I wanted to be able to access the action from the decorator page, for
> error messages display etc.
> 
> The problem is that at decorating-time the action is no longer on the
> value stack, and the VelocityDecoratorServlet doesn't use webwork's own
> context. A workaround was to grab the action from the attribute
> "webwork.valuestack.head" and to setup a valuestack containing just this
> action. The static class WebWorkVelocityContext is also a cut'n'paste
> from VelocityHelper (it has package access there, unfortunately).
> 
> Is there are better way ? Or shouldn't the decorator page have access to
> framework internals ?
> 
>         Jan
> 




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Opensymphony-sitemesh mailing list
Opensymphony-sitemesh@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensymphony-sitemesh
[prev in list] [next in list] [prev in thread] [next in thread]