required version of Xerces?

> IS the EXistServlet really needing Xerces 2.8.1 specifically?
>
>
> 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> Warning: Failed find a valid Parser!
>
> JDK 1.5.0_02
> Orbeon Forms Release 3.6.0beta.200711080716
> OC4J 10.1.3.3.0
> orion-web.xml for ops.war has been changed to have the following line enabled.
>
>   <web-app-class-loader search-local-classes-first="true"
> include-war-manifest-class-path="true" />
>
>
> Thanks,
> JL
>

> Jean-Luc,
>
> This may be a question for the exist-open mailing-list. Which version of
> Orbeon Forms are you using? Recent builds of Orbeon Forms include eXist
> 1.1.1.
>
> -Erik
>
>
> Jean Luc wrote:
> > IS the EXistServlet really needing Xerces 2.8.1 specifically?
> >
> >
> > 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
> > Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> > Warning: Failed find a valid Parser!
> >
> > JDK 1.5.0_02
> > Orbeon Forms Release 3.6.0beta.200711080716
> > OC4J 10.1.3.3.0
> > orion-web.xml for ops.war has been changed to have the following line enabled.
> >
> >   <web-app-class-loader search-local-classes-first="true"
> > include-war-manifest-class-path="true" />
> >
> >
> > Thanks,
> > JL
> >
>
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
> --
> 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
>
>

> 3.6.0beta.200711080716 (see original email).
>
> Do I need to worry about this if I only want to use Orbeon as an
> XForms engine for now?
>
> Thanks,
> JL
>
> On Nov 8, 2007 1:46 PM, Erik Bruchez <[hidden email]> wrote:
>> Jean-Luc,
>>
>> This may be a question for the exist-open mailing-list. Which version of
>> Orbeon Forms are you using? Recent builds of Orbeon Forms include eXist
>> 1.1.1.
>>
>> -Erik
>>
>>
>> Jean Luc wrote:
>>> IS the EXistServlet really needing Xerces 2.8.1 specifically?
>>>
>>>
>>> 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
>>> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
>>> Warning: Failed find a valid Parser!
>>>
>>> JDK 1.5.0_02
>>> Orbeon Forms Release 3.6.0beta.200711080716
>>> OC4J 10.1.3.3.0
>>> orion-web.xml for ops.war has been changed to have the following line enabled.
>>>
>>>   <web-app-class-loader search-local-classes-first="true"
>>> include-war-manifest-class-path="true" />
>>>
>>>
>>> Thanks,
>>> JL
>>>
>>
>> --
>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
>> http://www.orbeon.com/
>>
>>
>> --
>> 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
>>
>>

> The XForms engine does use eXist now to store state data:
>
> http://www.orbeon.com/blog/2007/10/29/a-disk-based-xforms-state-store-for-orbeon-forms/
>
> Now whether that eXist error will prevent this to work, I don't know!
> Can you give it a try? You will see exceptions popping up if the XForms
> engine doesn't manage to store data into eXist. The Government Forms
> example also won't work.
>
> -Erik
>
>
> Jean Luc wrote:
> > 3.6.0beta.200711080716 (see original email).
> >
> > Do I need to worry about this if I only want to use Orbeon as an
> > XForms engine for now?
> >
> > Thanks,
> > JL
> >
> > On Nov 8, 2007 1:46 PM, Erik Bruchez <[hidden email]> wrote:
> >> Jean-Luc,
> >>
> >> This may be a question for the exist-open mailing-list. Which version of
> >> Orbeon Forms are you using? Recent builds of Orbeon Forms include eXist
> >> 1.1.1.
> >>
> >> -Erik
> >>
> >>
> >> Jean Luc wrote:
> >>> IS the EXistServlet really needing Xerces 2.8.1 specifically?
> >>>
> >>>
> >>> 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
> >>> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> >>> Warning: Failed find a valid Parser!
> >>>
> >>> JDK 1.5.0_02
> >>> Orbeon Forms Release 3.6.0beta.200711080716
> >>> OC4J 10.1.3.3.0
> >>> orion-web.xml for ops.war has been changed to have the following line enabled.
> >>>
> >>>   <web-app-class-loader search-local-classes-first="true"
> >>> include-war-manifest-class-path="true" />
> >>>
> >>>
> >>> Thanks,
> >>> JL
> >>>
> >>
> >> --
> >> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> >> http://www.orbeon.com/
> >>
> >>
> >> --
> >> 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
> >>
> >>
>
>
> --
>
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
> --
> 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
>
>

> It doesn't work indeed, I cannot even see the default page (error
> details below). The errors are eXist-related.
>
> I see two problems here.
>
> (1) the actual error message is weird because the entry session id and
> the actual session id are ... identical. Can it be a case of string
> comparison done with == instead of equals() ?
>
> Inconsistent session ids when persisting XForms state store entry
> (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).
>
>
> (2) I see eXist also complains about not finding Xalan and Saxon.
> However, these ARE packaged in ops.war and the application server
> (oc4j) is set to look first at the war's own libraries. This is a
> packaging issue that should be fixed (please :-)
>
>
> 2007-11-08 16:24:33,229 WARN  EXistServlet  - Looking for a valid Parser...
> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> Warning: Failed find a valid Parser!
> Please add an appropriate Parser to the class-path, e.g. in the
> 'endorsed' folder of the servlet container or in the 'endorsed' folder
> of th
> e JRE.
> 2007-11-08 16:24:33,245 WARN  EXistServlet  - Looking for a valid Transformer...
> Checking for Xalan, not found!
> Checking for Saxon, not found!
> Warning: Failed find a valid Transformer!
>
>
> It's possible that problem #2 causes (indirectly?) #1.
>
>
>
>
> Java stack trace:
>
> org.orbeon.oxf.common.OXFException
> Message Inconsistent session ids when persisting XForms state store
> entry (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).
> Servlet Stack Trace (198 method calls)
>
> Class Name Method Name File Name Line Number
> org.orbeon.oxf.xforms.state.XFormsPersistentApplicationStateStore add
> XFormsPersistentApplicationStateStore.java 131
> org.orbeon.oxf.xforms.state.XFormsStateManager
> getInitialEncodedClientState XFormsStateManager.java 125
> org.orbeon.oxf.xforms.processor.handlers.XHTMLBodyHandler start
> XHTMLBodyHandler.java 100
> org.orbeon.oxf.xml.ElementHandlerController startElement
> ElementHandlerController.java 161
> org.orbeon.oxf.xml.ForwardingContentHandler startElement
> ForwardingContentHandler.java 87
> org.orbeon.oxf.xml.ElementFilterContentHandler startElement
> ElementFilterContentHandler.java 41
> org.orbeon.oxf.xforms.processor.XFormsToXHTML$4 startElement
> XFormsToXHTML.java 382
> org.orbeon.oxf.xml.SAXStore replay SAXStore.java 193
> org.orbeon.oxf.xforms.processor.XFormsToXHTML outputResponseDocument
> XFormsToXHTML.java 363
> org.orbeon.oxf.xforms.processor.XFormsToXHTML doIt XFormsToXHTML.java 226
>  More...
>
> Call stack:
> oxf:/config/xforms-widgets.xsl 27 N/A converting XHTML+XForms document
> to XHTML
> oxf:/ops/pfc/xforms-epilogue.xpl 122 68 reading processor output name
> → document id → xhtml-data  <p:output name="document"
> id="xhtml-data"/>
> oxf:/ops/pfc/xforms-epilogue.xpl 128 67 reading processor output name
> → data ref → xformed-data  <p:output name="data" ref="xformed-data"/>
> oxf:/config/epilogue.xpl 44 58 reading processor output name →
> xformed-data id → xformed-data  <p:output name="xformed-data"
> id="xformed-data"/>
> oxf:/config/epilogue-servlet.xpl 31 48 reading processor output name →
> xformed-data <p:param type="input" name="xformed-data"/>
> oxf:/config/epilogue.xpl 62 46 executing processor name →
> {http://www.orbeon.com/oxf/processors}pipeline <p:processor
> name="oxf:pipeline">...</p:processor>
> oxf:/apps/forms/page-flow.xml 65 47 executing processor name →
> {http://www.orbeon.com/oxf/processors}pipeline
> oxf:/page-flow.xml 44 106 reading page model data output page id →
> appsmodel → apps/${1}/page-flow.xml  <page id="apps"
> path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher"
> model="apps/${1}/page-flow.xml"/>
>
>
>
>
>
> On Nov 8, 2007 2:17 PM, Erik Bruchez <[hidden email]> wrote:
> > The XForms engine does use eXist now to store state data:
> >
> > http://www.orbeon.com/blog/2007/10/29/a-disk-based-xforms-state-store-for-orbeon-forms/
> >
> > Now whether that eXist error will prevent this to work, I don't know!
> > Can you give it a try? You will see exceptions popping up if the XForms
> > engine doesn't manage to store data into eXist. The Government Forms
> > example also won't work.
> >
> > -Erik
> >
> >
> > Jean Luc wrote:
> > > 3.6.0beta.200711080716 (see original email).
> > >
> > > Do I need to worry about this if I only want to use Orbeon as an
> > > XForms engine for now?
> > >
> > > Thanks,
> > > JL
> > >
> > > On Nov 8, 2007 1:46 PM, Erik Bruchez <[hidden email]> wrote:
> > >> Jean-Luc,
> > >>
> > >> This may be a question for the exist-open mailing-list. Which version of
> > >> Orbeon Forms are you using? Recent builds of Orbeon Forms include eXist
> > >> 1.1.1.
> > >>
> > >> -Erik
> > >>
> > >>
> > >> Jean Luc wrote:
> > >>> IS the EXistServlet really needing Xerces 2.8.1 specifically?
> > >>>
> > >>>
> > >>> 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
> > >>> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> > >>> Warning: Failed find a valid Parser!
> > >>>
> > >>> JDK 1.5.0_02
> > >>> Orbeon Forms Release 3.6.0beta.200711080716
> > >>> OC4J 10.1.3.3.0
> > >>> orion-web.xml for ops.war has been changed to have the following line enabled.
> > >>>
> > >>>   <web-app-class-loader search-local-classes-first="true"
> > >>> include-war-manifest-class-path="true" />
> > >>>
> > >>>
> > >>> Thanks,
> > >>> JL
> > >>>
> > >>
> > >> --
> > >> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> > >> http://www.orbeon.com/
> > >>
> > >>
> > >> --
> > >> 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
> > >>
> > >>
> >
> >
> > --
> >
> > Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> > http://www.orbeon.com/
> >
> >
> > --
> > 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
> >
> >
>

> It doesn't work indeed, I cannot even see the default page (error
> details below). The errors are eXist-related.
>
> I see two problems here.
>
> (1) the actual error message is weird because the entry session id and
> the actual session id are ... identical. Can it be a case of string
> comparison done with == instead of equals() ?
>
> Inconsistent session ids when persisting XForms state store entry
> (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).

> (2) I see eXist also complains about not finding Xalan and Saxon.
> However, these ARE packaged in ops.war and the application server
> (oc4j) is set to look first at the war's own libraries. This is a
> packaging issue that should be fixed (please :-)
>
>
> 2007-11-08 16:24:33,229 WARN  EXistServlet  - Looking for a valid Parser...
> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> Warning: Failed find a valid Parser!
> Please add an appropriate Parser to the class-path, e.g. in the
> 'endorsed' folder of the servlet container or in the 'endorsed' folder
> of th
> e JRE.
> 2007-11-08 16:24:33,245 WARN  EXistServlet  - Looking for a valid Transformer...
> Checking for Xalan, not found!
> Checking for Saxon, not found!
> Warning: Failed find a valid Transformer!

> Found the answer to problem #1: session ids (Strings) are indeed
> compared with != instead of !equals() in
> XFormsPersistentApplicationStateStore.java:131 :-)
>
>                 if (session.getId() != sessionId)
>
>
>
> On Nov 8, 2007 4:34 PM, Jean Luc <[hidden email]> wrote:
>> It doesn't work indeed, I cannot even see the default page (error
>> details below). The errors are eXist-related.
>>
>> I see two problems here.
>>
>> (1) the actual error message is weird because the entry session id and
>> the actual session id are ... identical. Can it be a case of string
>> comparison done with == instead of equals() ?
>>
>> Inconsistent session ids when persisting XForms state store entry
>> (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
>> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).
>>
>>
>> (2) I see eXist also complains about not finding Xalan and Saxon.
>> However, these ARE packaged in ops.war and the application server
>> (oc4j) is set to look first at the war's own libraries. This is a
>> packaging issue that should be fixed (please :-)
>>
>>
>> 2007-11-08 16:24:33,229 WARN  EXistServlet  - Looking for a valid Parser...
>> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
>> Warning: Failed find a valid Parser!
>> Please add an appropriate Parser to the class-path, e.g. in the
>> 'endorsed' folder of the servlet container or in the 'endorsed' folder
>> of th
>> e JRE.
>> 2007-11-08 16:24:33,245 WARN  EXistServlet  - Looking for a valid Transformer...
>> Checking for Xalan, not found!
>> Checking for Saxon, not found!
>> Warning: Failed find a valid Transformer!
>>
>>
>> It's possible that problem #2 causes (indirectly?) #1.
>>
>>
>>
>>
>> Java stack trace:
>>
>> org.orbeon.oxf.common.OXFException
>> Message Inconsistent session ids when persisting XForms state store
>> entry (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
>> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).
>> Servlet Stack Trace (198 method calls)
>>
>> Class Name Method Name File Name Line Number
>> org.orbeon.oxf.xforms.state.XFormsPersistentApplicationStateStore add
>> XFormsPersistentApplicationStateStore.java 131
>> org.orbeon.oxf.xforms.state.XFormsStateManager
>> getInitialEncodedClientState XFormsStateManager.java 125
>> org.orbeon.oxf.xforms.processor.handlers.XHTMLBodyHandler start
>> XHTMLBodyHandler.java 100
>> org.orbeon.oxf.xml.ElementHandlerController startElement
>> ElementHandlerController.java 161
>> org.orbeon.oxf.xml.ForwardingContentHandler startElement
>> ForwardingContentHandler.java 87
>> org.orbeon.oxf.xml.ElementFilterContentHandler startElement
>> ElementFilterContentHandler.java 41
>> org.orbeon.oxf.xforms.processor.XFormsToXHTML$4 startElement
>> XFormsToXHTML.java 382
>> org.orbeon.oxf.xml.SAXStore replay SAXStore.java 193
>> org.orbeon.oxf.xforms.processor.XFormsToXHTML outputResponseDocument
>> XFormsToXHTML.java 363
>> org.orbeon.oxf.xforms.processor.XFormsToXHTML doIt XFormsToXHTML.java 226
>>  More...
>>
>> Call stack:
>> oxf:/config/xforms-widgets.xsl 27 N/A converting XHTML+XForms document
>> to XHTML
>> oxf:/ops/pfc/xforms-epilogue.xpl 122 68 reading processor output name
>> → document id → xhtml-data  <p:output name="document"
>> id="xhtml-data"/>
>> oxf:/ops/pfc/xforms-epilogue.xpl 128 67 reading processor output name
>> → data ref → xformed-data  <p:output name="data" ref="xformed-data"/>
>> oxf:/config/epilogue.xpl 44 58 reading processor output name →
>> xformed-data id → xformed-data  <p:output name="xformed-data"
>> id="xformed-data"/>
>> oxf:/config/epilogue-servlet.xpl 31 48 reading processor output name →
>> xformed-data <p:param type="input" name="xformed-data"/>
>> oxf:/config/epilogue.xpl 62 46 executing processor name →
>> {http://www.orbeon.com/oxf/processors}pipeline <p:processor
>> name="oxf:pipeline">...</p:processor>
>> oxf:/apps/forms/page-flow.xml 65 47 executing processor name →
>> {http://www.orbeon.com/oxf/processors}pipeline
>> oxf:/page-flow.xml 44 106 reading page model data output page id →
>> appsmodel → apps/${1}/page-flow.xml  <page id="apps"
>> path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher"
>> model="apps/${1}/page-flow.xml"/>
>>
>>
>>
>>
>>
>> On Nov 8, 2007 2:17 PM, Erik Bruchez <[hidden email]> wrote:
>>> The XForms engine does use eXist now to store state data:
>>>
>>> http://www.orbeon.com/blog/2007/10/29/a-disk-based-xforms-state-store-for-orbeon-forms/
>>>
>>> Now whether that eXist error will prevent this to work, I don't know!
>>> Can you give it a try? You will see exceptions popping up if the XForms
>>> engine doesn't manage to store data into eXist. The Government Forms
>>> example also won't work.
>>>
>>> -Erik
>>>
>>>
>>> Jean Luc wrote:
>>>> 3.6.0beta.200711080716 (see original email).
>>>>
>>>> Do I need to worry about this if I only want to use Orbeon as an
>>>> XForms engine for now?
>>>>
>>>> Thanks,
>>>> JL
>>>>
>>>> On Nov 8, 2007 1:46 PM, Erik Bruchez <[hidden email]> wrote:
>>>>> Jean-Luc,
>>>>>
>>>>> This may be a question for the exist-open mailing-list. Which version of
>>>>> Orbeon Forms are you using? Recent builds of Orbeon Forms include eXist
>>>>> 1.1.1.
>>>>>
>>>>> -Erik
>>>>>
>>>>>
>>>>> Jean Luc wrote:
>>>>>> IS the EXistServlet really needing Xerces 2.8.1 specifically?
>>>>>>
>>>>>>
>>>>>> 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
>>>>>> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
>>>>>> Warning: Failed find a valid Parser!
>>>>>>
>>>>>> JDK 1.5.0_02
>>>>>> Orbeon Forms Release 3.6.0beta.200711080716
>>>>>> OC4J 10.1.3.3.0
>>>>>> orion-web.xml for ops.war has been changed to have the following line enabled.
>>>>>>
>>>>>>   <web-app-class-loader search-local-classes-first="true"
>>>>>> include-war-manifest-class-path="true" />
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> JL
>>>>>>
>>>>> --
>>>>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
>>>>> http://www.orbeon.com/
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>>
>>>>>
>>>
>>> --
>>>
>>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
>>> http://www.orbeon.com/
>>>
>>>
>>> --
>>> 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
>>>
>>>

> I am having difficulty using xforms:setvalue with dates. The following line
> is causing an error.
>
> <xforms:setvalue ref="instance('main-doc')/End_Date"
> value="instance('main-doc')/Start_Date + xs:yearMonthDuration('P1Y')  -
> xs:dayTimeDuration('P1D')" />
>
> The error is:
>
> XForms error: Unsuitable operands for arithmetic operation
> (xdt:untypedAtomic, xdt:yearMonthDuration)

> I am having difficulty using xforms:setvalue with dates. The following
> line is causing an error.
>
> <xforms:setvalue ref="instance('main-doc')/End_Date"
> value="instance('main-doc')/Start_Date + xs:yearMonthDuration('P1Y')  
> - xs:dayTimeDuration('P1D')" />
>
> The error is:
>
> XForms error: Unsuitable operands for arithmetic operation
> (xdt:untypedAtomic, xdt:yearMonthDuration)

> Thanks, I committed a fix for this!
>
> -Erik
>
>
> Jean Luc wrote:
> > Found the answer to problem #1: session ids (Strings) are indeed
> > compared with != instead of !equals() in
> > XFormsPersistentApplicationStateStore.java:131 :-)
> >
> >                 if (session.getId() != sessionId)
> >
> >
> >
> > On Nov 8, 2007 4:34 PM, Jean Luc <[hidden email]> wrote:
> >> It doesn't work indeed, I cannot even see the default page (error
> >> details below). The errors are eXist-related.
> >>
> >> I see two problems here.
> >>
> >> (1) the actual error message is weird because the entry session id and
> >> the actual session id are ... identical. Can it be a case of string
> >> comparison done with == instead of equals() ?
> >>
> >> Inconsistent session ids when persisting XForms state store entry
> >> (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
> >> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).
> >>
> >>
> >> (2) I see eXist also complains about not finding Xalan and Saxon.
> >> However, these ARE packaged in ops.war and the application server
> >> (oc4j) is set to look first at the war's own libraries. This is a
> >> packaging issue that should be fixed (please :-)
> >>
> >>
> >> 2007-11-08 16:24:33,229 WARN  EXistServlet  - Looking for a valid Parser...
> >> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> >> Warning: Failed find a valid Parser!
> >> Please add an appropriate Parser to the class-path, e.g. in the
> >> 'endorsed' folder of the servlet container or in the 'endorsed' folder
> >> of th
> >> e JRE.
> >> 2007-11-08 16:24:33,245 WARN  EXistServlet  - Looking for a valid Transformer...
> >> Checking for Xalan, not found!
> >> Checking for Saxon, not found!
> >> Warning: Failed find a valid Transformer!
> >>
> >>
> >> It's possible that problem #2 causes (indirectly?) #1.
> >>
> >>
> >>
> >>
> >> Java stack trace:
> >>
> >> org.orbeon.oxf.common.OXFException
> >> Message Inconsistent session ids when persisting XForms state store
> >> entry (entry session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54,
> >> actual session id: 0a40025f22b85a67018e023646a49df8cbbb90548a54).
> >> Servlet Stack Trace (198 method calls)
> >>
> >> Class Name Method Name File Name Line Number
> >> org.orbeon.oxf.xforms.state.XFormsPersistentApplicationStateStore add
> >> XFormsPersistentApplicationStateStore.java 131
> >> org.orbeon.oxf.xforms.state.XFormsStateManager
> >> getInitialEncodedClientState XFormsStateManager.java 125
> >> org.orbeon.oxf.xforms.processor.handlers.XHTMLBodyHandler start
> >> XHTMLBodyHandler.java 100
> >> org.orbeon.oxf.xml.ElementHandlerController startElement
> >> ElementHandlerController.java 161
> >> org.orbeon.oxf.xml.ForwardingContentHandler startElement
> >> ForwardingContentHandler.java 87
> >> org.orbeon.oxf.xml.ElementFilterContentHandler startElement
> >> ElementFilterContentHandler.java 41
> >> org.orbeon.oxf.xforms.processor.XFormsToXHTML$4 startElement
> >> XFormsToXHTML.java 382
> >> org.orbeon.oxf.xml.SAXStore replay SAXStore.java 193
> >> org.orbeon.oxf.xforms.processor.XFormsToXHTML outputResponseDocument
> >> XFormsToXHTML.java 363
> >> org.orbeon.oxf.xforms.processor.XFormsToXHTML doIt XFormsToXHTML.java 226
> >>  More...
> >>
> >> Call stack:
> >> oxf:/config/xforms-widgets.xsl 27 N/A converting XHTML+XForms document
> >> to XHTML
> >> oxf:/ops/pfc/xforms-epilogue.xpl 122 68 reading processor output name
> >> → document id → xhtml-data  <p:output name="document"
> >> id="xhtml-data"/>
> >> oxf:/ops/pfc/xforms-epilogue.xpl 128 67 reading processor output name
> >> → data ref → xformed-data  <p:output name="data" ref="xformed-data"/>
> >> oxf:/config/epilogue.xpl 44 58 reading processor output name →
> >> xformed-data id → xformed-data  <p:output name="xformed-data"
> >> id="xformed-data"/>
> >> oxf:/config/epilogue-servlet.xpl 31 48 reading processor output name →
> >> xformed-data <p:param type="input" name="xformed-data"/>
> >> oxf:/config/epilogue.xpl 62 46 executing processor name →
> >> {http://www.orbeon.com/oxf/processors}pipeline <p:processor
> >> name="oxf:pipeline">...</p:processor>
> >> oxf:/apps/forms/page-flow.xml 65 47 executing processor name →
> >> {http://www.orbeon.com/oxf/processors}pipeline
> >> oxf:/page-flow.xml 44 106 reading page model data output page id →
> >> appsmodel → apps/${1}/page-flow.xml  <page id="apps"
> >> path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher"
> >> model="apps/${1}/page-flow.xml"/>
> >>
> >>
> >>
> >>
> >>
> >> On Nov 8, 2007 2:17 PM, Erik Bruchez <[hidden email]> wrote:
> >>> The XForms engine does use eXist now to store state data:
> >>>
> >>> http://www.orbeon.com/blog/2007/10/29/a-disk-based-xforms-state-store-for-orbeon-forms/
> >>>
> >>> Now whether that eXist error will prevent this to work, I don't know!
> >>> Can you give it a try? You will see exceptions popping up if the XForms
> >>> engine doesn't manage to store data into eXist. The Government Forms
> >>> example also won't work.
> >>>
> >>> -Erik
> >>>
> >>>
> >>> Jean Luc wrote:
> >>>> 3.6.0beta.200711080716 (see original email).
> >>>>
> >>>> Do I need to worry about this if I only want to use Orbeon as an
> >>>> XForms engine for now?
> >>>>
> >>>> Thanks,
> >>>> JL
> >>>>
> >>>> On Nov 8, 2007 1:46 PM, Erik Bruchez <[hidden email]> wrote:
> >>>>> Jean-Luc,
> >>>>>
> >>>>> This may be a question for the exist-open mailing-list. Which version of
> >>>>> Orbeon Forms are you using? Recent builds of Orbeon Forms include eXist
> >>>>> 1.1.1.
> >>>>>
> >>>>> -Erik
> >>>>>
> >>>>>
> >>>>> Jean Luc wrote:
> >>>>>> IS the EXistServlet really needing Xerces 2.8.1 specifically?
> >>>>>>
> >>>>>>
> >>>>>> 2007-11-08 13:27:28,091 WARN  EXistServlet  - Looking for a valid Parser...
> >>>>>> Checking for Xerces, found version Xerces-J 2.9.1 needed version Xerces-J 2.8.1
> >>>>>> Warning: Failed find a valid Parser!
> >>>>>>
> >>>>>> JDK 1.5.0_02
> >>>>>> Orbeon Forms Release 3.6.0beta.200711080716
> >>>>>> OC4J 10.1.3.3.0
> >>>>>> orion-web.xml for ops.war has been changed to have the following line enabled.
> >>>>>>
> >>>>>>   <web-app-class-loader search-local-classes-first="true"
> >>>>>> include-war-manifest-class-path="true" />
> >>>>>>
> >>>>>>
> >>>>>> Thanks,
> >>>>>> JL
> >>>>>>
> >>>>> --
> >>>>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> >>>>> http://www.orbeon.com/
> >>>>>
> >>>>>
> >>>>> --
> >>>>> 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
> >>>>>
> >>>>>
> >>>
> >>> --
> >>>
> >>> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> >>> http://www.orbeon.com/
> >>>
> >>>
> >>> --
> >>> 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
> >>>
> >>>
>
>
> --
>
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>
>
> --
> 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
>
>