This is where I stopped playing with MutableFormDefinition -- the changed definition has to be stored somewhere, but just in a module global isn't very good. If it was stored in the session it should be more persistent.
On Sun, 2002-03-10 at 16:45, Luke Opperman wrote: > Hi - > > Just realized the source of a few troubles we've been > having. MutableFormDefinitionStore disappears whenever the > appserver reloads the FFK.Form module (restarting the > appserver, using oneshot, etc). This means that if you > submit a form after an appserver reload, form processing > dies when trying to find a suitable formDefinition from the > dynamic _formID_. (KeyError for the dynamic serial.) > > I've played with a few options, the best one for me right > now seems to be to throw out the dynamic store entirely, > letting forms keep their original name when mutated. This > would work for us, since we are only using once-mutated > forms (never a mutated version and its parent on the same > page). But clearly this doesn't work for more complex uses > of mutable forms... > > Thoughts on persistently storing unique system-wide form > definitions? > > 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 > _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
