Action handlers (OPS3.0)

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

Action handlers (OPS3.0)

chary-2
Erik,

The xforms submission specifies an action attribute. Also, in pageflow
one can specify an action element.
If I have a submit button in an XSL file along with a submission id, PFC
will arrange to invoke the specified page
based on the path-name indicated in the submission element. More over,
in pageflow, the <page> element can also specify an action.

1. xsl file: (model)
    <submission action="/foo/action"..../>

2. page-flow.xml

 case 1:
    <page path-name="/foo" ..>     <!-- foo is the first page with a
view containing the button -->
        <action>...                          <!-- the submit button when
clicked will invoke this action -->

 case 2:
    <page path-name="foo" model="  .." view=".."> <!-- when submit is
clicked, the action in /foo/action is invoked -->
      <!-- no action here.. -->

     <page path-name="/foo/action" ..>            
        <action>....                      

My question is how to specify the action in page-flow.xml (case 1 or
case 2)?
When is it appropriate to define <action> in the page flow?


Thanks,
Chary









--
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: Action handlers (OPS3.0)

Erik Bruchez
Administrator
chary wrote:

> Erik,
>
> The xforms submission specifies an action attribute. Also, in pageflow
> one can specify an action element.
> If I have a submit button in an XSL file along with a submission id, PFC
> will arrange to invoke the specified page
> based on the path-name indicated in the submission element. More over,
> in pageflow, the <page> element can also specify an action.
>
> 1. xsl file: (model)
>    <submission action="/foo/action"..../>
>
> 2. page-flow.xml
>
> case 1:
>    <page path-name="/foo" ..>     <!-- foo is the first page with a view
> containing the button -->
>        <action>...                          <!-- the submit button when
> clicked will invoke this action -->
>
> case 2:
>    <page path-name="foo" model="  .." view=".."> <!-- when submit is
> clicked, the action in /foo/action is invoked -->
>      <!-- no action here.. -->
>
>     <page path-name="/foo/action" ..>                  
> <action>....                    
> My question is how to specify the action in page-flow.xml (case 1 or
> case 2)?
> When is it appropriate to define <action> in the page flow?
XForms introduces a greater separation between the "page" and "services"
associated with the page, thanks to the submission model. This means
that some new patterns now need to be considered, and there is still
work to do in this area.

I think that when you can consider an action such as "save document" as
a generic service, which may or may not be called from XForms, it is
good to declare it in a separate PFC page. This is true in particular
when the service returns XML and does not require to navigate away from
the page.

When the action is strictly used by the page, and/or the action
potentially requires navigating away from the current page, then
declaring it within the initial page element is probably better, as it
makes the action local, and also concentrates page navigation under the
outer page element.

-Erik



--
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