Hi, I think you can use WicketTester for it: http://cwiki.apache.org/WICKET/testing-pages.html
Use this method to dump the page: http://wicket.apache.org/docs/1.4/org/apache/wicket/util/tester/BaseWicketTester.html#dumpPage%28%29 Frido Casper Bang wrote: > > Hi Ashley, > > I actually wrote the list regarding a similar idea about a year ago. It > seems like a handy thing for RAD and for newbies struggling with keeping > simple CRUD pages in sync. However I can offer nothing but an > encurraging "great idea, go for it". :) > > /Casper > > > Igor Vaynberg wrote: >> i dont see why it wouldnt be possible. if you can instantiate a page >> you can use a visitor to visit all the components and generate >> approximately appropriate markup. >> >> perhaps if you had something working you would get more interest. >> >> -igor >> >> On Mon, Nov 9, 2009 at 1:57 AM, Ashley Aitken <mrhat...@mac.com> wrote: >> >>> Dear All, >>> >>> I have seen a feature in Wicket Bench (I think it is) that can >>> automatically >>> generate the Web component object construction hierarchy for a given Web >>> form with Wicket ids. It's a neat feature. However, I am wondering if >>> it >>> would be possible to do the reverse. >>> >>> Could Wicket classes be extended to automatically generate the HTML file >>> (based on the Wicket object hierarchy) if the HTML file doesn't already >>> exist? Obviously, it couldn't generate the non-dynamic HTML aspects of >>> a >>> Web page, but at least it could provide a skeleton page? >>> >>> This could be configured to overwrite (or not) existing files each time >>> the >>> code changed. Perhaps it could be configured to include (for debugging >>> purposes) some Wicket information for each item in the page (almost like >>> a >>> RAD solution but the intention is not for RAD). >>> >>> Perhaps it could even use a form of the "generation gap pattern" by >>> putting >>> each dynamic chunk into a separate HTML file and then #include them into >>> a >>> main HTML file which it doesn't get overwritten. Though I'm not sure >>> how >>> this would exactly work ... >>> >>> I've seen Wicket RAD and Wicket Web Beans but these are not what I am >>> thinking about. Eventually, I would want a graphics / Web designer to >>> complete the page around the skeleton dynamic HTML parts (that perhaps >>> Wicket has autogenerated). >>> >>> I know this would never be the full solution but it may allow one to >>> concentrate just on the Java code and not even have to worry about the >>> HTML >>> to start with. I think it could be an interesting approach. Is this >>> possible? Has this already been done? >>> >>> Any comments appreciate. >>> >>> Cheers, >>> Ashley. >>> >>> >>> -- >>> Ashley Aitken >>> Perth, Western Australia >>> mrhatken at mac dot com >>> Skype Name: MrHatken (GMT + 8 Hours!) >>> >>> >>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> 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 >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View this message in context: http://old.nabble.com/Autogenerating-HTML-files-...--tp26263720p26271589.html Sent from the Wicket - User 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
