cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: JXForms vs. Woody vs. KISS
Date Mon, 27 Oct 2003 18:07:58 GMT

On 27.10.2003 18:43, Oleg Dulin wrote:

> If the requirement is simply to show a form based on an XML file, let 
> the user edit it, validate it, and then save the updates, then this can 
> be easier done with a simple pipeline and I see no reason to deal with a 
> yet another framework outside of Cocoon.
> Here is an example:
> - I have an XML document
> - I want to prepopulate an HTML form and present it to ther user based 
> on the values in document
> - The user edits the form and clicks "Save"
> - The values are extracted out of POST parameters and saved back to the 
> original document.
> First two points are trivial, because all one needs to do is transform 
> original document into an HTML form.
> The remainder is tricky. I accomplished this by setting up an internal 
> pipeline that uses RequestGenerator to create an XSL transform called 
> "update.xsl" that applies the changes to the original document. To know 
> which form values go to which places in the original document I used 
> xpaths of the original elements and attributes as names for input 
> fields. So, an XSL can be generated that applies the changes to the 
> original doc and wraps it in something that SOurceWritingTransformer can 
> understand.
> Is there a Cocoon solution that would let me easily set up a form that 
> essentially edit XML w/o all of the aforementioned convoluted XSLTs ? To 
> rephrase -- is there a way to map XML document onto an HTML form and 
> then apply the changes back to the original document other than what I 
> mentioned ?  Would Chicoon or Woody be helpful ?

Of course! This is exactly what Woody can do for you. Have a look on the 
binding sample which changes an XML file.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message