Thanks Michael for the hint. I already adapt that example and this is working - at least in parts.
Those are my two pain points at the moment: 1.) share one session 2.) seperate Login page Regarding 1.): I've implemented two Links. Both do need a authentication so both xxxApplication.java extend AuthenticatedWebApplication and provide the methods getHomepage(), getWebSessionClass(), getSignInPageClass() and init(). In both xxxApplication.java files the methot getWebSessionClass return MyAuthenticatedWebSession.class. But, if I first click on link 1 I get a redirect to the login page. After successfully login I get the content of link 1. If I click link 1 again no login is necesarry. After that I click on link 2 (which also needs authentication) and get redirected to the login page again. But my assumption was that if I'm already marked as logged in I don't have to login again?!? Obviously I get another instance of the MyAuthenticatedWebSession.class. How can I avoid another login once I'm already logged in? Regarding 2.): Apart from the configuration of the xxxApplication.java files I want to offer the user a seperat login page. In fact I want to reuse the existing one for the two links. Because of the fact that this class is extending the SignInPage I don't have to care about input fields and onSubmit method. But if I call my login.html directly and submit the form I get the following exception: java.lang.ClassCastException: org.apache.wicket.protocol.http.WebSession. But within my html there is only < span wicket:id="signInPanel"/> and nothing within the associated java file. Thanks in advance. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/dynamic-navigation-side-content-depending-on-login-status-tp3384641p3386832.html Sent from the Users forum 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
