upgrade to NG XForms engine

Hi Hank,

Thank you for your answer!
I managed to solve the problem.
The problem was the same that you wrote: Orbeon wants to store the states of xforms.

I had to comment this property in the properties.xml:
        <!--property as="xs:string" name="oxf.xforms.state-handling" value="server"/-->

Thank you!

Laszlo

Hank Ratzesberger <[hidden email]> 2009.11.24 01:49 Please respond to [hidden email]

To [hidden email] cc Subject [ops-users] Re: upgrade to NG XForms engine

Hi Laszio,

Orbeon uses eXist internally to store the state of xforms and their sessions, so it
is a required library.

Not sure what this error means.  I have not used the default submission.

Did you begin with the full orbeon.war or an otherwise working configuration?

You may want to test submitting to another url mapped to an xpl service.

Sorry, but besides a few tests I can't help much here.

--Hank

On Nov 23, 2009, at 4:14 AM, [hidden email] wrote:


Hi All,

We are using Orbeon 3.6.0 at the moment, with Classic XForms engine.
We would like to upgrade our application, accordingly as the first step we want to use the NG XForms engine.
We have had  this modifications up to now:
       - changed  the "xforms" attribute to "default-submission" attribute in the page element on the page-flow.xml
       -  put the "xforms:model" element into the "xhtml:head" in the corresponding view

It seems to me everything is right, the right choose branch starts to execute

<p:choose href="#data">
 <!-- ========== Test for NG XForms engine ========== -->
 <p:when test="/xhtml:html/xhtml:head/xforms:model"><!-- TODO: test on result of processor above -->
....

but finally we always get the following execption:

Type        class org.exist.util.DatabaseConfigurationException
Message        Unable to read configuration file at {}
Location        oxf:/config/xforms-widgets.xsl
Line        19
Column        -1
Stack Trace        

org.exist.util.DatabaseConfigurationException: Unable to read configuration file at {}
       at org.exist.util.Configuration.<init>(Configuration.java:146)
       at org.exist.xmldb.DatabaseImpl.configure(DatabaseImpl.java:100)
       at org.exist.xmldb.DatabaseImpl.getLocalCollection(DatabaseImpl.java:176)
       at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:156)
       at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:151)
       at org.xmldb.api.DatabaseManager.getCollection(Unknown Source)
       at org.orbeon.oxf.processor.xmldb.XMLDBProcessor.getCollection(XMLDBProcessor.java:155)
       at org.orbeon.oxf.processor.xmldb.XMLDBProcessor.executeQuery(XMLDBProcessor.java:251)
       at org.orbeon.oxf.processor.xmldb.XMLDBProcessor.query(XMLDBProcessor.java:174)
......


even tough we don't use exist at all.

Why we can get this error message?
Can anybody help?
Thanks!

Laszlo


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
OW2 mailing lists service home page: http://www.ow2.org/wws

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042





--
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