On 7/20/06, Jan Zach <[EMAIL PROTECTED]> wrote:
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.
That's just how page-based application frameworks work. The url generated to reach the next view is based on the existing view name -- it doesn't represent the page source code. You can use redirect tags in your navigation cases to fix this where the transition between one page and the next is stateless (ie, you'll lose all messages and savestate and other request-scoped data when you add a redirect tag).
