After searching a bit, I found that AbstractTransformerBehavior replaces the RequestCycle.response temporarly to put its own, between beforeRender en afterRender methods, whereas other classes manipulates the response during that phase, so when AbstractTransformerBehavior puts back the "original" response, it is no more the "official" response. In fact I'm not sure that AbstractTransformerBehavior is for me, i'm going to write my own behavior which doesn't keep the "orginal" response. First tests seem promising.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Interpolate-response-with-IResponseFilter-tp4651476p4651529.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
