Why don't you just have two pages, one that is the HTML form and submits the data, one that gets the data and displays it back again depending on that data.
Saving the markup is a bad IMO, if the original form needs to change, even slightly, you are still using the old markup on the other side. Best to just use the data from that form. cheers, Steve On 03/02/2010, at 11:51 AM, Branden Tanga wrote: > Hello, > > This particular form is dynamic, in that it may be different for each user. > As a business rule, I have to be able to build back this exact form as read > only in another part of the application. > > What I was doing originally, was parsing all of the wicket components on the > java side, extracting their objectModelAsString and id, and putting those > into an xml. Then when I needed to build the form back as read only, I would > parse the xml and build back the markup. The other day I had an epiphany and > realized, why don't I just store the markup from the original form, it would > be much simpler and less prone to errors. > > The only catch is that I have to get the markup with the user input > (checkboxes checked, textboxes with text, etc.). So I need to capture the > state of the markup at the moment that the user hits the submit button on > the form. > > > To All: As soon as I'm back to my regular desktop I'll work on your > suggestions. Thanks! > > Thanks, > Branden Tanga > Programmer / EHR Systems Engineer > > > On Tue, Feb 2, 2010 at 5:57 AM, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > >> why? >> >> -igor >> >> On Mon, Feb 1, 2010 at 3: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 >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
