Thanks for the tip, I'll read up on the archive and look at switching
to client side saving.
Jesse
Heath Borders wrote:
Switch to client state-saving. Unfortunately, this is the only solution.
If you search the archives, I believe I outlined the technical reason
for this problem.
On Wed, 19 Jan 2005 10:47:43 -0500, Jesse Vitrone <[EMAIL PROTECTED]> wrote:
sure, reason is <commandLink/> uses POST of HTTP.
<redirect/> in
faces-config.xml's navigation rulez
will do the trick.
If I understood you
right... :-)
Yes, that's exactly what I was looking for, thanks. Now that the URL looks
right, that exposes another problem I'm having that I thought this would've
fixed.
I have a page with 2 command links, I click linkA, it takes me to another
page, then I hit the back button and click linkB. LinkB doesn't work any
more, it just reloads the page when I click it. I'm guessing because it's
not finding the from-view-id properly when it's looking for the navigation
rule? Is there a nice little trick around this problem too?
Thanks again.
|
