Hello all - Question for Ian and anyone else: What is the reason for _processForm (in FormServlet) having two checks to try to find the currentForm? Let me rephrase: When would a request not have _formID_ and yet still want/need to be processed?
Our situation is probably a complete bastardization of the intents of FFK and Webware, but we have a page that creates a mutable formdefinition in __init__, modifies it in awake, then on sucessful submission calls app.forward() to a subclass of this page. (So it relies on the superclass to create the formdef, and then in awake modifies it for new purposes, keeping some common fields.) So we were running into a problem where the new page would start processing the form again, find __formID__, and call the submit methodToInvoke in what became an infinite loop. So the 'solution' seemed to be to delete the __formID__ request field in the methodToInvoke. Which is when we found that we also needed to delete the submit field... it seems to us that if there's no __formID__ then it is an unhappy coincidence if there is a request field with the same name as a submit field. Again, let me rephrase: What is the situation where I don't have a formID field but really wanted FFK to process my form for me anyways? Thanks, btw Mutable forms are entirely cool and proving very useful in general. Luke ===== ------------------ Reference Counting Garbage Collection: Look out philosophy majors, things really DO cease to exist when no one is looking at them! ------------------ __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
