On Sunday, Feb 23, 2003, at 16:01 US/Pacific, Christopher Oliver wrote:
I've committed changes to support using the Cocoon flow layer with XMLForm, which includes a flow-based version of the XMLForm feedback sample wizard (http://localhost:8888/samples/xmlform/flow), that you'll be able to try yourself as soon as someone fixes the build for the samples in cvs ;)
Great stuff, Chris!
What are the build problems that you mentioned?
Note: in this implementation there is a 1-1 mapping between validation phases and views.
Please test these changes and let me know if they work and if they make sense.
The Cocoon flow layer now supports using JavaScript objects as well as Java beans, DOM and JDOM objects (or anything else compatible with JXPath, see http://jakarta.apache.org/commons/jxpath).
This means you can pass a JavaScript object to sendPage*() and access its properties with jpath:value-of in an xsp page. It also means that the model you use for your XMLForm can be a JavaScript object.
I've added the XMLForm JavaScript API to system.js (http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/java/ org/apache/cocoon/components/flow/javascript/ system.js?rev=1.7&content-type=text/plain)
Here is a summary of the methods of the JavaScript XForm:
[...]
/**
* Sends view to a presentation pipeline but doesn't wait for submission
* All continuations associated with the form are invalidated.
*
* @param view view to send
* @param uri presentation pipeline uri
*/
finish([String] view, [String] uri)
[...]
I think 'finish' is too generic, it can refer to anything. Can we rename it to finishForm instead?
Regards, Ovidiu
