I had exactly the same problem yesterday. The problem was that I was
using directly the sourcePage parameter instead getSourcePage() and it
was forwarding to the encryped URL.
The behavior seems normal. I couldn't see a document on the site
describing "How to upgrade" but now I see that the
The source page parameter is encrypted in 1.5 but was not in 1.4.
And as Luther pointed out, TypeConverterFactory#add() method is
newly added in 1.5 (in 1.4, the add() method is defined in the
DefaultTypeConverterFactory).
So, my guess is that the old stripes.jar is in your web container's
global
I ended up was overwriting the getSourcePageResolution() in my
ActionBeanContext to return new ForwardResolution(this.getSourcePage());
Something is pretty strange in the behavior.
Regards
Morten
2009/2/25 Ben Gunter
> That's an odd one. Check your ActionBeanContext.getSourcePage() to see if
That's an odd one. Check your ActionBeanContext.getSourcePage() to see if
it's doing something different. The _sourcePage parameter is always
encrypted for security reasons starting with 1.5, and the tail end of that
thing looks like an encrypted string. The only way I would expect to see
something
When updating to Stripes 1.5 from 1.4 I ran into problems when a user
submits a form where validation breaks.
It seems that the encoded source page parameter sends the user to a
wrong url when this happens.
How do I ensure that submits that does not validate sends the user
back to the source_page
When updating to Stripes 1.5 from 1.4 I ran into problems when a user
submits a form where validation breaks.
It seems that the encoded source page parameter sends the user to a
wrong url when this happens.
How do I ensure that submits that does not validate sends the user
back to the source_page
