Problems upgrading to recent snapshot

> Hi guys,
>
> I've been upgrading from 3.5.0.200702202124 to 3.6.0beta.200708070321
> and have a problem with my xforms submission elements.
>
> I have a site written using jsp documents and deployed together with the
> orbeon WAR. My upgrade process has been to run directory diff's of the
> new nightly build with my current version and overwrite any specific
> files which have been updated.
>
> After doing this I have found my initial Xform pages load file but
> whenever I attempt to issue a submission with action="do.jsp"
> replace="instance" - I find that it goes into an infinite loop with
> do.jsp being called repeatedly by different processors. Finally Orbeon
> produces the following:
>
> 2007-08-08 11:32:39,760 http-8080-Processor24 ERROR
> xslt.XSLTTransformer  - Error at line 81 of
> oxf:/ops/utils/formatting/xml-formatting.xsl:
> Too many nested apply-templates calls. The stylesheet may be looping.
> 2007-08-08 11:32:39,916 http-8080-Processor24 ERROR
> processor.XFormsServer - XForms - submission - xforms-submit-error
> throwable: java.lang.StackOverflowError [...]
>
> If I change replace="all" the submission is displayed correctly.
> Any idea what went wrong or where to look with my upgrade?
>
> Chris.
>
>

> Chris,
>
> I think we had a related post recently but I can't find it. I suspect you
> have the exact same case, due to xforms-value-changed events dispatched
> upon instance replacement. If you trigger a submission with
> xforms-value-changed, then you get an infinite loop: xforms-value-changed
> -> submission -> xforms-value-changed -> submission -> etc.
>
> The workaround is to protect your submission with a flag, for example:
>
> <xforms:action ev:event="xforms-value-changed" if="flag != 'true'">
>    <xforms:setvalue ref="flag">true</xforms:setvalue>
>    <xforms:send submission="my-submission"/>
>    <xforms:setvalue ref="flag">false</xforms:setvalue>
> </xforms:action>
>
> The reason you are getting too many xforms-value-changed upon instance
> replacement is an altogether different problem, but the fix is not an
> easy one.
>
> -Erik
>
> Chris Bailey wrote:
>> Hi guys,
>>
>> I've been upgrading from 3.5.0.200702202124 to 3.6.0beta.200708070321
>> and have a problem with my xforms submission elements.
>>
>> I have a site written using jsp documents and deployed together with the
>> orbeon WAR. My upgrade process has been to run directory diff's of the
>> new nightly build with my current version and overwrite any specific
>> files which have been updated.
>>
>> After doing this I have found my initial Xform pages load file but
>> whenever I attempt to issue a submission with action="do.jsp"
>> replace="instance" - I find that it goes into an infinite loop with
>> do.jsp being called repeatedly by different processors. Finally Orbeon
>> produces the following:
>>
>> 2007-08-08 11:32:39,760 http-8080-Processor24 ERROR
>> xslt.XSLTTransformer  - Error at line 81 of
>> oxf:/ops/utils/formatting/xml-formatting.xsl:
>> Too many nested apply-templates calls. The stylesheet may be looping.
>> 2007-08-08 11:32:39,916 http-8080-Processor24 ERROR
>> processor.XFormsServer - XForms - submission - xforms-submit-error
>> throwable: java.lang.StackOverflowError [...]
>>
>> If I change replace="all" the submission is displayed correctly.
>> Any idea what went wrong or where to look with my upgrade?
>>
>> Chris.
>>

> Ah yes thanks a lot Eric
>
> I found the previous post you were talking about:
> <http://www.nabble.com/Problem-with-xforms-value-changed%2C-incremental%3D%22true%22-and-replace%3D%22instance%22-tf4093453.html#a11643534>
> and notice a tracker has been set up for it.
>
> Cheers,
> Chris.
>
>
> --On 08 August 2007 13:52 +0200 Erik Bruchez <[hidden email]> wrote:
>
>> Chris,
>>
>> I think we had a related post recently but I can't find it. I suspect you
>> have the exact same case, due to xforms-value-changed events dispatched
>> upon instance replacement. If you trigger a submission with
>> xforms-value-changed, then you get an infinite loop: xforms-value-changed
>> -> submission -> xforms-value-changed -> submission -> etc.
>>
>> The workaround is to protect your submission with a flag, for example:
>>
>> <xforms:action ev:event="xforms-value-changed" if="flag != 'true'">
>>    <xforms:setvalue ref="flag">true</xforms:setvalue>
>>    <xforms:send submission="my-submission"/>
>>    <xforms:setvalue ref="flag">false</xforms:setvalue>
>> </xforms:action>
>>
>> The reason you are getting too many xforms-value-changed upon instance
>> replacement is an altogether different problem, but the fix is not an
>> easy one.
>>
>> -Erik
>>
>> Chris Bailey wrote:
>>> Hi guys,
>>>
>>> I've been upgrading from 3.5.0.200702202124 to 3.6.0beta.200708070321
>>> and have a problem with my xforms submission elements.
>>>
>>> I have a site written using jsp documents and deployed together with the
>>> orbeon WAR. My upgrade process has been to run directory diff's of the
>>> new nightly build with my current version and overwrite any specific
>>> files which have been updated.
>>>
>>> After doing this I have found my initial Xform pages load file but
>>> whenever I attempt to issue a submission with action="do.jsp"
>>> replace="instance" - I find that it goes into an infinite loop with
>>> do.jsp being called repeatedly by different processors. Finally Orbeon
>>> produces the following:
>>>
>>> 2007-08-08 11:32:39,760 http-8080-Processor24 ERROR
>>> xslt.XSLTTransformer  - Error at line 81 of
>>> oxf:/ops/utils/formatting/xml-formatting.xsl:
>>> Too many nested apply-templates calls. The stylesheet may be looping.
>>> 2007-08-08 11:32:39,916 http-8080-Processor24 ERROR
>>> processor.XFormsServer - XForms - submission - xforms-submit-error
>>> throwable: java.lang.StackOverflowError [...]
>>>
>>> If I change replace="all" the submission is displayed correctly.
>>> Any idea what went wrong or where to look with my upgrade?
>>>
>>> Chris.
>>>
>
>
>