Timothy Larson wrote:
In woody.js [1] there was a change in version 1.6 that stopped calling:
cocoon.request.setAttribute(this.attrName, this.form);
and did this instead:
var bizData = { woody-form: this.form };
indeed, this lines up more with how flow is expected to be working
This will
Marc Portier wrote:
in terms of best practice I would probably be advocating the use of
jxtemplate in combinaion with flow rather then xsp
+1
JXTemplate is massive but works nice and dandy.
/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source,
IMO the change to use woody-form is very poor choice because its not a
valid Jexl identifier. This means that if you want to access it in
JXTemplate you have to use this syntax:
${flowContext['woody-form'].someWidget}
If you change it to say 'woodyForm' you can access it directly:
Thanks for the help.
So far, this is the only way I have gotten this to work.
In the flow change:
cocoon.sendPage(success-pipeline);
to:
cocoon.sendPage(success-pipeline, {woody:form.getModel()});
and in a JXTemplate file use this syntax to get the value of the
name widget:
h3Name:
://cocoon.apache.org/2.1/userdocs/flow/index.html
Chris
-Original Message-
From: Timothy Larson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2003 12:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Need help fixing a Woody flow sample
Thanks for the help.
So far, this is the only way I have gotten
In woody.js [1] there was a change in version 1.6 that stopped calling:
cocoon.request.setAttribute(this.attrName, this.form);
and did this instead:
var bizData = { woody-form: this.form };
This will require a change in this part of form1_success.xsp [2]:
// get reference to form and some of
