Hmmm, now you mention it. I did come across a curios issue: https://github.com/wicketstuff/core/blob/master/jdk-1.5-parent/wicket- security-parent/wasp- parent/wasp/src/test/java/org/apache/wicket/security/GeneralTest.java#L326
This testcase opens the HomePage, clicks a link on this page, which adds a secure panel. This causes a redirect to the LoginPage. All goes well to this point, but then: when the login form is submitted, the original link is clicked again, from within form.submit(). Is this how WicketTester is supposed to behave? Best regards, Emond On Thursday 07 April 2011 11:36:46 Martin Grigorov wrote: > And you did this without finding a single bug in Wicket 1.5 ?! :-) > > Congrats! > > On Thu, Apr 7, 2011 at 11:31 AM, Emond Papegaaij > <emond.papega...@topicus.nl > > > wrote: > > > > Hi all, > > > > I just migrated wicket-security to wicket 1.5 and moved it into > > Wicketstuff- > > core. As this is my first commit on Wicketstuff-core, I would really > > appreciate it if someone could check if I did everything the way it is > > supposed to be done. > > > > Wicket-security for Wicket 1.4 lives in its own GitHub repository under > > dashorst/wicketstuff-security. I added this repo as a remote, and fetched > > it > > into a branch, moved some things around and merged the branch into > > master. As > > far as I can see, this kept the history intact. Next, I updated the poms > > to make them work with the Wicketstuff parent pom, using other projects > > as example. Finally, I fixed all errors and testcases. > > > > Best regards, > > Emond Papegaaij
