cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: FileWritingTransformer
Date Fri, 15 Feb 2002 21:49:40 GMT
> From: Jeremy Quinn [mailto:jeremy@media.demon.co.uk]
> 
> At 2:00 pm -0500 15/2/02, Vadim Gritsenko wrote:
> >> From: Jeremy Quinn [mailto:jeremy@media.demon.co.uk]
> >
> ><snip/>
> >
> >> >Question #2: do you check if the <xfwt:write> element includes
*one*
> >> >and
> >> >only *one* nested element? If not, we could end up with problems
> >> >later on.
> >
> >Wait, why such a limitation? What if you want to write few files, not
> >one? The result modes of the transformer might be:
> > - exception in case of error,
> > - <xfwt:result/> tag
> >
> >
> >> No I don't, I'll add that to my list, thanks.
> >
> >Please reconsider this addition :)
> 
> I thought he meant something different ....
> 
> ie. make sure the document you make, cannot have more than one root by
> mistake.

Oops! My bad :)


> Not, make sure there is only one <xfwt> tag in the whole stream.
> 
> I'd like to be able to modify more than one file at once if required
as well.

Cool.

<snip/>

> >> Which is the right way to go do you think?
> >
> >I think there is no need (and may be even harm) to have xfwt
namespace
> >declared needlessly.
> 
> 
> Unless I am to buffer the whole document before Serializing it, I do
not
> understand how I can tell that the part I am Serializing to file is
going
> to have something in the xfwt namespace before I have to start prefix
> mapping.

Hm. May be then leave this namespace; better way to handle this may
arise later, after some usage of transformer.

Vadim


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message