XForms losing action element (not content)

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

XForms losing action element (not content)

Colin O'Brien
Hi,

I've just created a couple of new xforms and when the user clicks
submit the instance that arrives back at the server has the value of
the action as set by the submit but doesn't have the element around it
(and so isn't recognizable in pageflow/pipeline/xsl).
So I get
save
instead of
<action>save</action>
Indeed this happens if I comment out the xforms:setvalue and hardcode
the value in the instance sent to the browser.
The only workaround I have found is to wrap the action element in an
action element - that is
<action><action>save</action></action>
This delivers the correct instance
<action>save</action>
to the server.

Haven't been able to spot what I am doing different between existing
forms that do not show this behavior and these new forms.
Before I delved any deeper into it, I wanted to check if anyone else is
(or has) seen this and if they know what the cause/fix might be (but
now I have seen it in a second form, I know it is not my imagination!)

Thanks & regards
Colin




--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: XForms losing action element (not content)

Alessandro  Vernet
Administrator
Hi Colin,

Are you seeing this with XForms NG? I don't think I have ever seen
anything similar.  Of course we would be interested if you can create
an example that shows the problem and that we can run locally.

Alex

On 1/11/06, Colin O'Brien <[hidden email]> wrote:

> Hi,
>
> I've just created a couple of new xforms and when the user clicks
> submit the instance that arrives back at the server has the value of
> the action as set by the submit but doesn't have the element around it
> (and so isn't recognizable in pageflow/pipeline/xsl).
> So I get
> save
> instead of
> <action>save</action>
> Indeed this happens if I comment out the xforms:setvalue and hardcode
> the value in the instance sent to the browser.
> The only workaround I have found is to wrap the action element in an
> action element - that is
> <action><action>save</action></action>
> This delivers the correct instance
> <action>save</action>
> to the server.
>
> Haven't been able to spot what I am doing different between existing
> forms that do not show this behavior and these new forms.
> Before I delved any deeper into it, I wanted to check if anyone else is
> (or has) seen this and if they know what the cause/fix might be (but
> now I have seen it in a second form, I know it is not my imagination!)
>
> Thanks & regards
> Colin
>
>
>
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet