Re: [Xsltforms-support] Cancelling loop/action

[Josselin M. <mor...@gm...>]

That was the error message I had 2 years ago “submission-in-progress“, and then I switched to my "while loop" and modified my submission routine to avoid this issue. I also checked my message element and it seems to be in the good place, in my <xf:submission /> I have  : 
<xf:action ev:event="xforms-submit-error">
    <xf:message level="modal">
        error:
        error-type: <output value="event('error-type')"/>
        error-message: <output value="event('error-message')"/>
        response-status-code: <output value="event('response-status-code')"/>
        response-reason-phrase: <output value="event('response-reason-phrase')"/>
        resource-uri: <output value="event('resource-uri')"/>
    </xf:message>
</xf:action>
But I just tried it and I noticed that I get the error messages with the submission for my main instance, but not with the submission for my secondary instance (this one). Are you running XSLTForms 1.5?

As you suggested, I also tried the dispatch method with @delay='0’ and it doesn’t work either, but with @delay=‘1' yes (before it was running with @delay='1000’)…

I’ll make a sample, but the form is running with BaseX ant it’s quite big, I need to remove all unnecessary stuff to share it. 

Thank you very much for your help and sharing!
Best,
Josselin. 

> Le 5 févr. 2021 à 11:26, Steven Pemberton <ste...@cw...> a écrit :
> 
> I added a test case to the XForms test suite to test for this case, and indeed XSLTForms incorrectly returns "submission-in-progress" if you do a <send/> in the handler for submit-done (apparently you put the message element in the wrong place).
> 
> Steven
> 
> On Thursday 04 February 2021 23:42:37 (+01:00), Josselin Morvan wrote:
> 
> Hi Steven, 
> 
> Thank you for your quick response. Unfortunately, all the error events are empty.
> So, I tried your method with the dispatch element. At first it didn’t work either, then I added a delay to the dispatch and… it works!
> As I said, when the submission is done, I update my instance with the server’s response (@xml:id and @localType value, etc.) and then I perform the next submission, maybe all these actions are asynchronous or performed simultaneously, and it produces a conflict? The @delay would allow to really execute the next submission at the end of the entire process?
> 
> Best, 
> Josselin.
> 
>> Le 4 févr. 2021 à 22:25, Steven Pemberton <ste...@cw... <mailto:ste...@cw...>> a écrit :
>> 
>> <message>Submission error.       
>> 		  error-type: <output value="event('error-type')"/>
>> 		  error-message: <output value="event('error-message')"/>
>> 		  response-status-code: <output value="event('response-status-code')"/>
>> 		  response-reason-phrase: <output value="event('response-reason-phrase')"/>
>> 		  resource-uri: <output value="event('resource-uri')"/>
>> 	       </message>
> 
> 
> --