Hi Joerg, I tried to do exactly that, but I got that error about 'not bound'. In my form definition, I do have that line:
<wd:selection-list src="cocoon:/mychoices.xml" dynamic="true"/> and then the pipeline for mychoices.xml leads to an xml document with this text: <wd:selection-list> <wd:item value="1"/> <wd:item value="2"/> <wd:item value="3"> </wd:selection-list> What does that error mean? And what might be going wrong? > On 27.04.2004 20:25, Billie wrote: > > > I did look at the WoodyDatatypeReference page, but I didn't understand. > When I tried to > > do just what you said there, I got an error 'The prefix "wd" for element > "wd:selection- > > list" is not bound' and I'm not sure what it means. When you say "transform > it to the > > format Woody expects"... what format is that? > > Billie > > <wd:selection-list src="cocoon:/mychoices.xml" dynamic="true"/> > > is part of the form definition, not the binding. It points to another > pipeline matching on mychoices.xml that provides a data structure like > the following one: > > <wd:selection-list> > <wd:item value="1"/> > <wd:item value="2"/> > <wd:item value="3"> > <wd:label>three</wd:label> > </wd:item> > <wd:item value="4"/> > <wd:item value="5"/> > </wd:selection-list> > > >>whereby mychoices.xml would match on a sitemap pipeline which could e.g. > >>use ESQL or the SqlTransformer to execute the query, and then transform > >>it to the format woody expects by using an XSLT. > > And this XML structure can be easily created using ESQL (XSP), > SQLTransformer and maybe an additional XSLT. This is exactly what Bruno > wrote. > > Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
