Re: Sitemesh and Ajax

On 12/11/06, Ian Roughley <[email protected]> wrote:
> I'm a little surprised that the clean-up filter goes before the webwork
> filter.  Are you using the ActionContext in custom written decorators?
>

In case you are using ActionContext in your decorators then the
required order is the one in the documentation. However, as everybody
else have already pointed out: I really cannot see any compelling
reason to apply the decorators to the AJAX responses.

./alex
--
.w( the_mindstorm )p.

> /Ian
>
>
>
> Jay Bose wrote:
> > I am using WebWork-2.2.4 and the Sitemesh-2.2.1.
> >
> > In the Webwork2 documentation for Sitemesh integration (http://wiki.opensymphony.com/display/WW/SiteMesh), users are directed to place the [b]ActionContextCleanUp[/b] 1st. Then the [b]SiteMesh filter[/b], and then the [b]FilterDispatcher[/b].
> >
> > I was having a problem getting requests to work within filtered pages, and as an experiment I moved the [b]Sitemesh filter[/b] [i]above[/i] the [b]ActionContextCleanUp[/b]. This gave me the filter chain below. After this, my ajax calls began to connect. Any ideas why this order works, and not the documented version?
> >
> > [code]
> >     <filter-mapping>
> >         <filter-name>sitemesh</filter-name>
> >         <url-pattern>/*</url-pattern>
> >     </filter-mapping>
> >
> >     <filter-mapping>
> >         <filter-name>webwork-cleanup</filter-name>
> >         <url-pattern>/*</url-pattern>
> >     </filter-mapping>
> >
> >     <filter-mapping>
> >         <filter-name>webwork</filter-name>
> >         <url-pattern>/*</url-pattern>
> >     </filter-mapping>
> > [/code]
> > ---------------------------------------------------------------------
> > Posted via Jive Forums
> > http://forums.opensymphony.com/thread.jspa?threadID=52858&messageID=106447#106447
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]