On Mon, 2003-10-27 at 22:24, joern turner wrote: > Oleg Dulin wrote: <snip/> > > The remainder is tricky. I accomplished this by setting up an internal > > pipeline that uses RequestGenerator to create an XSL transform called > > "update.xsl" that applies the changes to the original document. To know > > which form values go to which places in the original document I used > > xpaths of the original elements and attributes as names for input > > fields. So, an XSL can be generated that applies the changes to the > > original doc and wraps it in something that SOurceWritingTransformer can > > understand. > Chiba has a similar concept but without exposing xpathes of the instance > (for security reasons). it uses a mapping between xpathes and internally > generated ids.
You're pointing out two things here already people might not like about Chiba: - it assumes stateful operation (most of Woody also works stateless, thus without keeping any state on the server, which can be useful in some cases). - it uses meaningless id's as request parameter names -- 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]
