Isammoc OFF wrote: > > I don't really understand why you have two xxxApplication.java for only > two > links. In my mind, I would make only one xxxApplication.java for both > pages.
If both links would be on the same page - yes. But if you have several pages you need a separate xxxApplication.java file anyway (ok - not necessarily but in most of the cases). So let's assume there is a page A with a link and a page B with a link and both need authentication. Isammoc OFF wrote: > > This problem is common : Single Sign On (SSO). > IMHO, you may share cookies and check if the user is connected to the > other > application(s) thru web services. In fact there is only one application so from my point of view there is no need of implementing a SSO. The only thing I want to achieve is that a user don't have to login twice if he click on link A on page A and afterwards on link B on page B (both need authentication). There must be some easy solution for this issue, isn't it? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/dynamic-navigation-side-content-depending-on-login-status-tp3384641p3395024.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
