link model and view in separate deployment

Hi all

I have deployed ops as a separate war (nightly build). I have read that
you can not use the page-flow.xml when using this kind of setup. Is this
true? If so, how does this limit orbeon xforms capabilities for me? The
link between model and view seems to be made in the page-flow.xml which
is not available for my configuration. Is this correct ?

Also, I've been trying some XPL scripts, and though I can call them
directly using the correct URL, I don't seem to be able to call them
from a <xforms:submission/> tag. I tried different combinations, but
always get the error message : "Path ... does not start with a "/"
character". Here are some of the actions I tried to put in the
<xforms:submission> tag:

action="action.xpl"
action="/umadmin/xforms-jsp/lurch/action.xpl"
action="file://c:/unifiedpost/dev/UMAdmin-MI/exploded/xforms-jsp/lurch/a
ction.xpl"

Is this also a consequence of the separate deployment, or am I doing
something fundamentally wrong?

And as a followup on that question, how can I pass parameters to this
XPL script when calling it from my website? (to tell it what stylesheet
to use for example)

Thanks in advance,
Gerrit


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws

Gerrit Germis wrote:
> Hi all
>
> I have deployed ops as a separate war (nightly build). I have read that
> you can not use the page-flow.xml when using this kind of setup. Is this
> true? If so, how does this limit orbeon xforms capabilities for me? The
> link between model and view seems to be made in the page-flow.xml which
> is not available for my configuration. Is this correct ?

It shouldn't limit XForms capabilities. What it will do is prevent you
to use a *page model*. The good news is that you don't have to use a
page model to leverage XForms. (NOTE: On the other hand you will of
course have one or more XForms models in your XForms page.)

In separate deployment, you will usually either directly include initial
data in an XForms instance when you produce the page, or load initial
data using a submission run on the xforms-ready event directly from XForms.
You can't just call an XPL file from an action. You can either:

* Call a service, implemented typically by Orbeon Forms in a page flow
entry.

* Use the extension XPath function xxforms:call-xpl(), which allows you
for example to call XPL from xforms:setvalue, xforms:insert, or other
XForms actions. See:

http://www.orbeon.com/ops/doc/reference-xforms-2#ops-extensions

> And as a followup on that question, how can I pass parameters to this
> XPL script when calling it from my website? (to tell it what stylesheet
> to use for example)

When implementing a service in Orbeon Forms, you can POST an XML
document containing the parameters. This document will be available on
your XPL's "instance" input.

When using xxforms:call-xpl(), you can use any input you want as you
explicitly name inputs with that function.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


--
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
OW2 mailing lists service home page: http://www.ow2.org/wws