But in regards to your stateless page problem. Not only must the page be stateless, but also every component on the page. A form is not stateless, so you should use a StatelessForm on your login page. Also if a RestartResponseAtInterceptPage occurs (which is likely if you either use wicket-auth-roles or wicket-security) the session must be made non temporary to store the original page so you can later return to it. A couple of ways of avoiding this is to: - set the login page to the homepage - make sure all users access the loginpage directly instead of coming from the homepage (which sees the user needs to authenticate and throws the exception to redirect to the loginpage)
Maurice On Wed, Mar 12, 2008 at 12:26 PM, Maurice Marrink <[EMAIL PROTECTED]> wrote: > Its a patch for WicketTester, so not relevant for your situation. > That's why i asked first instead of blurting out noise like Johan did. :P > > Maurice > > On Wed, Mar 12, 2008 at 12:11 PM, Roberto Fasciolo > > <[EMAIL PROTECTED]> wrote: > > > > > > I'm talking about acceptance tests executed using selenium against the real > > application (we don't use WicketTester at all). > > > > What kind of patch do you have? > > > > -Roberto > > > > > > > > Mr Mean wrote: > > > > > > Are you talking about test behavior or real life app behavior? > > > > > > Maurice > > > > > > > -- > > View this message in context: > http://www.nabble.com/Strange-thing-in-Application-constructor-tp15786017p16001746.html > > > > > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
