I'm having an unusual case in which I would like to use javascript to load
and write pages into divs (somewhat ajax-like, but on other websites, as an
included tool). In order to do so, I want the rendered page to actually be
javascript alone the lines of:

var txt;
txt += "<p>some text here</p>";
txt += "<p>some text here</p>";
txt += ... etc
parent.writeintodiv("divname", txt);

so I can load this via a <script> tag on the website I want to integrate it
in.

In order to keep these pages maintainable, it would be really nice to be
able to 2-pass render wicket pages. Currently I am using a velocity 2-pass
renderservlet for that job. This works, but I would like to use wicket for
html rendering.

I'm having trouble finding out how to do this with wicket. Wicket pages seem
to directly render to the response. I would like to use the nice wicket HTML
rendering, but then intercept that, wrap it into the above javascript, and
output that.

Stuff I thought of myself:

- add my own markup stream filter, but they seem to filter tag by tag? I am
not sure how to implement that. 
- override the WebResponse servlet response, and intercept somewhere there.
however the factory for those seems to be application-wide?

What would be the best approach?

Thank you,

Christian

-- 
View this message in context: 
http://www.nabble.com/2-pass-rendering-tp14725201p14725201.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to