This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
This may be a stupid question, but I'm working with a JSF application and I'm seeing the URL that appears in the browser's navigation bar is always for the page I just left, rather than the page I'm on. Is that expected, or does it indicate something funny going on with the navigation? Functionally, the application seems to be fine. It displays the right content for the page, just the wrong URL. Even the document.location in the DOM has the URL of the previous page.
It's worth pointing out that if you use faces-redirect=true this introduces significant complications
regarding the passing of data between pages. For example if you select a department on page 1
to display a list of employees on page 2, you need to pass some sort of reference to the dept
between the pages. As the redirect results in a new request you end up having to store things
in the session map, flash "scope" (which I have have little success with) or use view parameters,
or CDI conversation scope.
When you throw ajax into the equation it gets even worse (until you switch from request to view
scope). These are things worth factoring into any design considerations, and a little prototyping
could save considerable amounts of heartache in the future.