RE: Javascript implementation limitation

I believe in XForms 1.1 you can do this, to implement post/redirect/get:

<xf:submission replace="instance" instance='foo' ... >
   <xf:load ev:event="xforms-submit-done" resource="instance('foo')/location" if="instance('foo')/location" />
</xf:submission>

In XForms 1.0 you needed to listen for xforms-enabled (or chiba-state-changed) on an xf:output bound to the location node, and it wasn't as reliable across implementations.

It may also work to do this (even in xsltforms, though I haven't checked)


<xf:submission replace="instance" instance='foo' ... >
   <xf:send ev:event="xforms-submit-done" submission="myget" />
</xf:submission>
<xf:submission id="myget" ... />

Leigh.

-----Original Message-----
From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf Of Joern Turner
Sent: Friday, December 04, 2009 1:01 AM
To: Mats Eklund
Cc: www-forms@w3.org
Subject: Re: Javascript implementation limitation

Mats,

On Dec 3, 2009, at 10:21 PM, Mats Eklund wrote:

> Hi,
>
>
> I'm weighing pros and cons of two xforms implementations, one is a 
> server side implementation and the other is a browser side 
> implementation in javascript. It appears to me that one inherent 
> limitation of a javascript implementation is that xforms submissions 
> with replace="all" is impossible to achieve. Any insights welcome?
>
That's not right. In Chiba we support submission/@replace="all".  
Though it comes to the price of having an additional URI param on the resulting URL. On the other hand you can always substitute a replace all with a combination of submission and load.

Regards,

Joern

>
> Thanks,
>
> Mats
>
>

Received on Thursday, 17 December 2009 18:15:44 UTC