On Tue, Jan 11, 2005 at 06:05:42PM +0100, Erik Bruchez wrote:
Can you try an instance-passing="forward" attribute on the root element of your page-flow.xml?
Doesn't have any effect (in WEB-INF/resources/page-flow.xml).
But I found two things that probably are the key to the solution, although *I* do not see the solution (yet):
- When I trace the HTML traffic, I see that first a POST is done, which is followed by a GET (or my /search URI)! Doesn't look good, does it?
- When I have a <result> element in my page-flow.xml *without* a page attribute (so, staying in the same page), the URI stays "clean". When I explicitly mention page="thispage" (its own page id), I do see the long URI's again.
Yes, this is exactly what the instance-passing="forward" controls: if set to "redirect", you get a redirect after the execution of an action if going to another page, if set to "forward" the redirection is done server-side and you don't have a client-side redirect (so you would only see a "post" when looking at the HTTP traffic).
But now the question is why would setting instance-passing="forward" not work? Do you have another page-flow.xml in use?
-Erik
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
