Erik Bruchez wrote:
I would like to hear Alex's confirmation, but I suspect that this may be due to the way the XForms instances are encoded in URLs. Passing a parameter named id=123 may be mistakenly interpreted by the XForms engine, which modifies your instance.
Yes, this is correct. In general, it is better to avoid using on the same page both XForms and your own URL parameters, as your URL parameters might conflict with those generated by the XForms engine. If you want still want to do this, use for your own parameters names that start with a "$", but note that this might change in the future.
This being said, when a page is loaded and this is not the result of an XForms form being submitted, the XForms engine does not need to the look at the request parameters. So in this particular case, you should not have a conflict. I have started investigating the issue and added a bug on SF.net to track the issue.
Alex
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
