Hi David, thanks for explaining. I was writing my own security filter (I did not want to use the tomcat one because I'm unable to set up pricipal programatically and probably it would not solve the problem) and this delay complicates the thing. If I would like to handle access restriction properly I'd have to have add another check into the navigation handler computing new state from current state, action, and configuration in addition to checks in servlet filter. Or am I wrong and there is a better way?
Regard jan ______________________________________________________________ > Od: [EMAIL PROTECTED] > Komu: "MyFaces Discussion" <[email protected]> > Datum: 20.07.2006 23:24 > Předmět: RE: one step delayed url > >Jan, > >That is the way myfaces works. If you want the URLs to match you'll >probably have to add the <redirect /> tag/parameter/attribute to your >navigation rules plus make sure that you put your beans in a scope where you >can use them in the next request if you need them such as a flash scope >(oops, nevermind that scope isn't myfaces), session scope, dialog scope, >SEAM (if you use it) conversation scope, etc. > >Regards, >David > >-----Original Message----- >From: Jan Zach [mailto:[EMAIL PROTECTED] >Sent: Thursday, July 20, 2006 4:29 PM >To: [email protected] >Subject: one step delayed url > > >Hi, don't you have anobody idea why url is laggin one step behind the actual >url of the application? For example the app is in /page1.jsf with navigation >control pointing to /page2.jsf. After firing the control the navigation >properly handles the request and /page2.jsf is displayed, however, in the >brower (and also in navigation handler) I'm getting /page1.jsf. The proper >url is shown after another step. > >I'm using myfaces 1.1.1, web.xml and faces-config in the attachment. > >Thanks >jan > > > > >
