Hi,
while playing with the provided Form Runner examples, I noticed that the summary page very aggressively caches the information extracted from the form.xhtml file: When I change, for example, the user-visible name of an element, or the internal name of the tag, the form itself is updated after a browser refresh. The summary page however still uses the old tags to fill the columns, and the old names as column headers. Restarting tomcat fixes this, but obviously that is not a good solution. Is there some way to trigger an internal "reload" of the form structure? I am using the latest stable version, 3.8. Kind regards, Ralf Jung -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
Ralf,
This probably comes from get-source-form-submission here: http://github.com/orbeon/orbeon-forms/blob/master/src/resources/apps/fr/includes/persistence-model.xml This caches the source of the form with xxforms:cache="true", which is pretty aggressive. This was solved by Form Builder invalidating that cache upon publish: http://github.com/orbeon/orbeon-forms/blob/master/src/resources/forms/orbeon/builder/form/dialog-publish.xml Are you using publish? If not, you could change xxforms;cache to "false", or, you could somehow run the xxforms:invalidate-instances action, which will empty that cache: http://wiki.orbeon.com/forms/doc/developer-guide/xforms-performance-settings -Erik On Fri, Oct 8, 2010 at 2:16 AM, Ralf Jung <[hidden email]> wrote: > Hi, > > while playing with the provided Form Runner examples, I noticed that the > summary page very aggressively caches the information extracted from the > form.xhtml file: When I change, for example, the user-visible name of an > element, or the internal name of the tag, the form itself is updated after a > browser refresh. The summary page however still uses the old tags to fill the > columns, and the old names as column headers. Restarting tomcat fixes this, but > obviously that is not a good solution. Is there some way to trigger an > internal "reload" of the form structure? > I am using the latest stable version, 3.8. > > Kind regards, > Ralf Jung > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Hi,
> This probably comes from get-source-form-submission here: > > http://github.com/orbeon/orbeon-forms/blob/master/src/resources/apps/fr/inc > ludes/persistence-model.xml > > This caches the source of the form with xxforms:cache="true", which is > pretty aggressive. > > This was solved by Form Builder invalidating that cache upon publish: > > http://github.com/orbeon/orbeon-forms/blob/master/src/resources/forms/orbeo > n/builder/form/dialog-publish.xml > > Are you using publish? > > If not, you could change xxforms;cache to "false", or, you could > somehow run the xxforms:invalidate-instances action, which will empty > that cache: > > http://wiki.orbeon.com/forms/doc/developer-guide/xforms-performance-setting > s copying the forms.xhtml around in the database? At any rate, I am not using Form Runner anymore since it turned out I need more flexibility and control about what's going on for this project. So I directly use XForms and custom XQuery scripts in the database. Kind regards, Ralf Jung -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |