Re: Need help fixing a Woody flow sample

[Christopher Oliver]

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:

${woodyForm.someWidget}

As far as Xsp, you should be able to access it using jpath:

<jpath:value-of select="woody-form/someWidget"/>

My $0.02,

Chris

Timothy Larson wrote:

Comments inline...

--- Marc Portier <[EMAIL PROTECTED]> wrote:
 

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

...
 

so shortest hack to me looks like adding
    cocoon.request.setAttribute("form1", form);
in front of:
    cocoon.sendPage("form1-success-pipeline");
   

I tried form, this.form, and form.form, but only form.form
worked without changing the XSP:
 cocoon.request.setAttribute("form1", form.form);
If you use this in the flowscript:
 cocoon.request.setAttribute("form1", form);
then in XSP how do you get from request.getAttribute("form1")
to a Form object?  I am not too sure how this java<->javascript
interfacing works yet.
 

in terms of best practice I would probably be advocating the use 
of jxtemplate in combinaion with flow rather then xsp

(which would avoid your question about jpath logicsheet as well)
   

I would still like to know the jpath answer, and also how to use
plain java to access a form held by the flow.  Do you know how/have
time to explain it?
--Tim Larson

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com