You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mark Horgan <me...@markhorgan.com> on 2003/01/12 23:09:34 UTC

ORB/JDO and XMLForms

Hi there,

I'm a new user of cocoon and I'm trying to get the form part of cocoon
setup. I've got XMLForms working, now I would like some way of automatically
putting the info into a database. I'm exploring a method used in O'Reilly's
Struts book that uses an ORM with the form javabean. Just wondering has
anybody got Apache's ORB with JDO working with Cocoon? (thought I might go
with JDO since it seems to be an emerging standard) Or maybe I should make a
custom javabean or action that automatically transfers the values to the db.

Thanks in advance,
Mark



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: ORB/JDO and XMLForms

Posted by Jakob Praher <jp...@yahoo.de>.
Am Son, 2003-01-12 um 23.09 schrieb Mark Horgan:
> Hi there,
> 
> I'm a new user of cocoon and I'm trying to get the form part of cocoon
> setup. I've got XMLForms working, now I would like some way of automatically
> putting the info into a database. I'm exploring a method used in O'Reilly's
> Struts book that uses an ORM with the form javabean. Just wondering has
> anybody got Apache's ORB with JDO working with Cocoon? (thought I might go
> with JDO since it seems to be an emerging standard) Or maybe I should make a
> custom javabean or action that automatically transfers the values to the db.
> 

right at the moment you could write the database access stuff in the
Action derived by AbstractXMLFormAction ...

in a project I am doing with XMLForm, I use an interface, FormLifecycle,
and an interface FormLifecycleListener. FormLifecycleListeners listens
for the following lifecycle events:

starting( ... )
completing( ... )
completed( ... )

abort( ... )

starting is called to denote that the form is starting, e.g. the data
model gets created.

completing is caleld to denote that the form is in completing mode ( the
listener can do a veto here)

completed is called to denote that the form is completed ( veto not
possible ).

abort is called when there is a non-normal abort has hapened.


whith this lifecycle listener there is a decomposition between the
business logic and the xml form action.


-- Jakob

> Thanks in advance,
> Mark
> 
> 
> 
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
> 
> To unsubscribe, e-mail:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>