JD, have you meanwhile succeeded in binding your repeater?

On Mon, 2003-11-17 at 16:53, JD Daniels wrote:
> Maybe a lil more info will get me some input :)
> 
> this is my flow:
> 
> function postInvoice(form) {
>       var uri = "cocoon://xml.xsp";
>       var resolver =
> cocoon.getComponent(Packages.org.apache.excalibur.source.SourceResolver.ROLE
> );
>       var source = resolver.resolveURI(uri);
>       var parser =
> cocoon.getComponent(Packages.org.apache.excalibur.xml.dom.DOMParser.ROLE);
>       var document =
> parser.parseDocument(Packages.org.apache.cocoon.components.source.SourceUtil
> .getInputSource(source));
> 
>       form.load(document);
> 
>       form.showForm("display-pipeline");
>       var model = form.getModel();
>       cocoon.sendPage("success-pipeline");
> }
> 
> I don't get an error, but the repeater rows do not show up either.
> 
> Template:
>       <wt:form-template action="#{$continuation/id}.continue" method="POST">
>       <!-- manual layout of fieldw, without use of a wi:group -->
>       <wt:widget-label id="ticket"/><br/>
>       <wt:repeater-size id="ticket"/>
>       <table border="1">
>         <tr>
>           <th><wt:repeater-widget-label id="ticket" widget-id="hours"/></th>
>           <th><wt:repeater-widget-label id="ticket" widget-id="user"/></th>
>           <th><wt:repeater-widget-label id="ticket"
> widget-id="client"/></th>
>           <th><wt:repeater-widget-label id="ticket"
> widget-id="project"/></th>
>           <th></th>
>         </tr>
> 
>         <!-- The contents of the repeater-widget element is a template that
> will
>         be applied to each row in the repeater. -->
>         <wt:repeater-widget id="ticket">
>           <tr>
>             <td><wt:widget id="hours"/></td>
>             <td><wt:widget id="user"/></td>
>             <td><wt:widget id="client"/></td>
>             <td><wt:widget id="project"/></td>
>             <td><wt:widget id="select"/></td>
>           </tr>
>         </wt:repeater-widget>
> 
>         <tr>
>           <td colspan="5" align="right">
>             <wt:widget id="deleteticket"/>
>           </td>
>         </tr>
>       </table>
> </wt:form-template>
> 
> Binding:
> 
> <wb:context xmlns:wb="http://apache.org/cocoon/woody/binding/1.0";
> xmlns:wd="http://apache.org/cocoon/woody/definition/1.0"; path="/">
>       <wb:value id="ticket" path="results/ticket"/>
>       <wb:value id="id" path="results/ticket/id"/>
>       <wb:value id="select" path="results/ticket/id"/>
>       <wb:value id="user" path="results/ticket/user"/>
>       <wb:value id="project" path="results/ticket/project"/>
>       <wb:value id="client" path="results/ticket/client"/>
>       <wb:value id="hours" path="results/ticket/hours"/>
> </wb:context>
> 
> 
> JD
> 
> -----Original Message-----
> From: JD Daniels [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 14, 2003 4:48 PM
> To: Cocoon Users
> Subject: Woody repeater with flow
> 
> 
> Say I have an xml document
> 
> <results>
>       <itemOne>
>               <name/>
>               <email>
>               <etc/>
>       </itemOne>
>       <itemOne>
>               <name/>
>               <email>
>               <etc/>
>       </itemOne>
>       <itemOne>
>               <name/>
>               <email>
>               <etc/>
>       </itemOne>
> </results>
> 
> How would I load this into a form, with repeater I have defined for itemOne.
> 
> Ie, I want to load a result set from a database, and display them all to the
> user as a bunch of repaters with wd:output widgets, with a select widget to
> remove them one by one before carrying on with an xsp to do something to the
> ones left. I am sure binding will do this, but I am using flow, and kinda
> lost as to how it actually will work. I have the template, definition, and
> binding files done, kinda lost at the flow part.
> 
> JD

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
[EMAIL PROTECTED]                          [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to