I guess you talk about IResponseFilter, not about IMarkupFilter. The latter is used only when the markup for a markup container is being loaded for the first time.
And yes, for non-Ajax requests the IResponseFilters are used when BufferedWebResponse is actually used: org.apache.wicket.protocol.http.BufferedWebResponse.WriteCharSequenceAction#invoke() For your needs it will work only with ONE_PASS_RENDER strategy. On Mon, Jun 18, 2012 at 5:25 PM, Martijn Dashorst <[email protected]> wrote: > BTW this is in wicket 1.5.x, but I assume this to be the case in 6.0 as well. > > Martijn > > On Mon, Jun 18, 2012 at 4:25 PM, Martijn Dashorst > <[email protected]> wrote: >> I'm building a HTML validation filter and noticed that the filters are >> not invoked when rendering to a buffered response, but only when the >> buffered response is sent to the browser. Is this by design? >> >> The issue I'm confronted with is that the request cycle doesn't know >> which page was rendered at that point (a >> BufferedWebResponseRequestHandler handler is handling the request), >> and it is impossible to render for example the class of the page, or >> set meta data information on the page. >> >> It was my assumption that the markup filters run in the same request >> that the response is generated, not when it is streamed to the client. >> >> Martijn >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
