At first I thought you would override the Component.onRender method to see
what is going back to the client and save that, but iterating through the
MarkupElements looks expensive (to rebuild the page) and might leave the
response in an unexpected state. Also though you could possibly override
WicketFilter.doFilter call to try and snag the response on render, but then
realized searching for <form> HTML specifically is going to suck.

I then found this example on getting Wicket components to cough up their
HTML into a dummy output stream that you can do what you want with:
http://www.danwalmsley.com/2008/10/21/render-a-wicket-page-to-a-string-for-html-email/

<http://www.danwalmsley.com/2008/10/21/render-a-wicket-page-to-a-string-for-html-email/>THEN
I was reading on the Wicket Wiki (the WiWi if you will) about rendering
Panels to Strings, which is essentially what I think you want to do, and
found this:
http://cwiki.apache.org/WICKET/rendering-panel-to-a-string.html#RenderingPaneltoaString-renderpanelstring

<http://cwiki.apache.org/WICKET/rendering-panel-to-a-string.html#RenderingPaneltoaString-renderpanelstring>--
I just included all the other resources incase they help with what you are
trying to do, wasn't clear on the use-case.

Have fun

On Mon, Feb 1, 2010 at 4:41 AM, Branden Tanga <branden.ta...@gmail.com>wrote:

> Hello,
>
> I would like to save a form's markup as a string when the form's submit
> button is pressed. The part that I am having difficulty with is
> understanding how to use wicket to grab a form's rendered markup. I have a
> feeling it must be pretty simple, but I'm getting lost in the wicket
> documentation. Any tips?
>
>
>
> Thanks,
> Branden Tanga
> Programmer / EHR Systems Engineer
>

Reply via email to