Hi Mike, I never tried myself to use what is explained on those links... so I cannot be of much help unless I start to guess things.
> > In this case, I am in the middle of a Wicket/http request and using > the BaseWicketTester as so: > > startPage(newly instantiated WebPage) > followed by > getServletResponse().getDocument() > > which works fine (however, it leaves the wicket:id=... tagsin the String) There is some flag you have to set at application level to strip Wikect tags from out put. Maybe that will solve that problem. > > BUT when I go to write out the current wicket/http request (not the > mock one from BaseWicketTester) it seems to be empty. > > Question: > 1. Could it be the case that using the MockWebApplication objects > still work on thread/request-specific session and response data? I > would explicitly hope this was NOT the case. > > 2. Perhaps the same HJttpServletResponse object is used for both the > MockApp and WicketApp? > > If this is the case, using the more complicated example may work as it > "hides" those objects by using its own (newly instatiated) subclass of > WicketApplication. > > Further Question: > 3. In this case, (seeing as I very new to Wicket and dont really get > it all yet) would I be missing some state in the WicketApplication > that my Page object is not going to have access too? Maybe you could find further info on using Wicket tester here http://cwiki.apache.org/WICKET/testing-pages.html Ernesto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
