Hi,
I just noticed a comment in the future Orbeon Forms 3.9 release a comment on state handling: •Faster XForms page state handling. ◦The state is now stored using EHcache. This is faster and consumes less memory than the Orbeon Forms 3.8 cache. Does this imply that eXist is no longer going to be used for state handling in Orbeon Forms. In fact, does this mean that the core of Orbeon Forms will not be dependent on eXist going forward? The reason I ask is that I am encountering numerous problems with the embedded eXist db and log files growing uncontrollably when loading resources and I am trying to assess if it warrants immediate investigation or is a problem that may just go away under OF 3.9. Thanks in advance for your help. Neil |
Administrator
|
Neil,
That's exactly right, the XForms engine itself no longer depends on eXist. eXist is still Orbeon Forms's / Form Runner's default database, but that's one level up and you can configure Orbeon to use a separately-deployed eXist or another database altogether.
So hopefully the problems you are seeing will go away with 3.9. You could already give the nightly builds a try. We have been ironing out lots of bugs and regressions lately and it's looking pretty good already.
-Erik On Tue, Feb 15, 2011 at 4:27 AM, ncrofts <[hidden email]> wrote:
-- 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 Erik,
The apps in question are using XForms, but not Form Runner as such. I'll look at the nightly builds as the dependency on eXist has been a concern for a while, as I've not had a particularly good experience with that in the past with performance issues and ever increasing log/dbx files. Thanks again for the feedback. Neil |
Free forum by Nabble | Edit this page |