Advise on multi-page xforms application

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

Advise on multi-page xforms application

wsalesky
I'm trying to migrate an application to Orbeon and am wondering if the best way to implement this is using the pipelines.
Essentially I have a login page, a queue of in-process items, and then a form for each type of metadata (Dublin Core and MODS). The current set up is a series of XQueries and XSL that ineract with eXist and use the Firefox extension.

Any advise on the best way to set up this sort of appication would be very helpful, any examples that you could point me to would also be useful.
Thanks for the help,
-Winona
 


--
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
Reply | Threaded
Open this post in threaded view
|

Re: Advise on multi-page xforms application

Alessandro Vernet
Administrator
Winona,

On Oct 10, 2008, at 6:40 AM, Winona Salesky wrote:

> I'm trying to migrate an application to Orbeon and am wondering if  
> the best way to implement this is using the pipelines.
> Essentially I have a login page, a queue of in-process items, and  
> then a form for each type of metadata (Dublin Core and MODS). The  
> current set up is a series of XQueries and XSL that ineract with  
> eXist and use the Firefox extension.

You are saying that you now have a series of XSLT and XQuery. Are  
those invoked by calling REST services with <xforms:submissions>, or  
is the XQuery/XSLT also used to produce XForms? If the later (produce  
XForms), then I would move that part in pipelines. If the former  
(implement "services" called by <xforms:submission>), then I would  
keep those where they are, I assume running out of eXist. Does this  
make sense, or is my understanding of your current architecture just  
too inaccurate? :)

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet



--
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
Reply | Threaded
Open this post in threaded view
|

Re: Re: Advise on multi-page xforms application

wsalesky
Hi Alex,
Sorry for the ambiguity in my question, my xforms are currently generated by xqueries, so it sounds like I do need to use pipelines. Are there any examples of multi-page forms using pipelines? All of the examples I looked at were single page examples.

I have a queue that is created by request to eXist for all in-process items, you get 25 items at a tme with the ability to page to the next 25, when you select an item you get an xform for either Dublin Core of MODS depending of the metadata returned by the query.

It is not terribly complex but I'm not sure how to use the pipelines to accomplish this. Again any examples would be really helpful.
Thanks,
-Winona

On Sat, Oct 18, 2008 at 2:36 PM, Alessandro Vernet <[hidden email]> wrote:
Winona,


On Oct 10, 2008, at 6:40 AM, Winona Salesky wrote:

I'm trying to migrate an application to Orbeon and am wondering if the best way to implement this is using the pipelines.
Essentially I have a login page, a queue of in-process items, and then a form for each type of metadata (Dublin Core and MODS). The current set up is a series of XQueries and XSL that ineract with eXist and use the Firefox extension.

You are saying that you now have a series of XSLT and XQuery. Are those invoked by calling REST services with <xforms:submissions>, or is the XQuery/XSLT also used to produce XForms? If the later (produce XForms), then I would move that part in pipelines. If the former (implement "services" called by <xforms:submission>), then I would keep those where they are, I assume running out of eXist. Does this make sense, or is my understanding of your current architecture just too inaccurate? :)

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet



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




--
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
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Advise on multi-page xforms application

Alessandro Vernet
Administrator
Winona,

On Oct 20, 2008, at 6:55 AM, Winona Salesky wrote:

> Sorry for the ambiguity in my question, my xforms are currently  
> generated by xqueries, so it sounds like I do need to use pipelines.  
> Are there any examples of multi-page forms using pipelines? All of  
> the examples I looked at were single page examples.
>
> I have a queue that is created by request to eXist for all in-
> process items, you get 25 items at a tme with the ability to page to  
> the next 25, when you select an item you get an xform for either  
> Dublin Core of MODS depending of the metadata returned by the query.

First, let's see if you can keep the system you currently have for  
generating XForms. After all, if you are happy with it, maybe you  
don't need pipelines. I imagine you are producing the XForms from  
eXist, right? If you are, you might be able to setup Orbeon Forms as a  
war along the eXist war, and setup an Orbeon Forms filter in the eXist  
war which would cause the XForms files produced by eXist to be  
processed by the Orbeon Forms war before they are sent to the browser  
which initiated the request. See the part relative to separate  
deployment on:

http://www.orbeon.com/ops/doc/reference-xforms-java

I have never done this with eXist, so I can't guarantee it will work,  
but it is worth a shot :).

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet



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