At 6:59 pm +0100 28/2/02, Sylvain Wallez wrote:
>Jeremy, could you please look at this for the SourceWritingTransformer ?
I think we just passed each other like ships in the night ;)
I'll get on to making the changes.
Thanks
regards Jeremy
--
__
Sylvain Wallez wrote:
> Jeremy Quinn wrote:
>>> As the first implementation supports atomic updates, and some other are
>>> likely do support it also, I was thinking of adding a rollback() method
>>> on WriteableSource. But rollback is more related to the OutputStream or
>>> ContentHandler th
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
> On Monday 25 February 2002 18:35, Sylvain Wallez wrote:
> >. . .
> > >Another argument is being able to use a CVS backend for versioning
> > >structured text documents stored in plain ASCII. AFAIK, this
> > > wouldn't work as well today with XML.
On Monday 25 February 2002 18:35, Sylvain Wallez wrote:
>. . .
> >Another argument is being able to use a CVS backend for versioning
> >structured text documents stored in plain ASCII. AFAIK, this
> > wouldn't work as well today with XML.
>
> Well, CVS doesn't really care of what's inside a versio
Bertrand Delacretaz wrote:
>On Monday 25 February 2002 15:26, Sylvain Wallez wrote:
>
>>. . .
>>Now what are the uses cases where we don't want to write XML ? There
>>may be cases where data is sent to the user or read from the request
>>in a non-xml format (such as structured text like discussed
On Monday 25 February 2002 15:26, Sylvain Wallez wrote:
>. . .
> Now what are the uses cases where we don't want to write XML ? There
> may be cases where data is sent to the user or read from the request
> in a non-xml format (such as structured text like discussed earlier
> about Chaperon), but
Jeremy Quinn wrote:
>At 12:22 am +0100 23/2/02, Sylvain Wallez wrote:
>
>>Jeremy, I also quickly updated the FileWritingTransformer so that it
>>uses any WriteableSource instead of just files. Could you please look at
>>it ? Another update would be also to the 'serializer' parameter fully
>>optio
Gianugo Rabellino wrote:
> Sylvain Wallez wrote:
>
>> Considering the discussions about the FileWritingTransformer, Cocoon
>> symetry and Stefano's source/drain RT, I added in
>> org.apache.cocoon.environment a new interface I already talked about :
>> WriteableSource. It adds writing methods to
Jeremy Quinn wrote:
>At 12:22 am +0100 23/2/02, Sylvain Wallez wrote:
>
>>Hi team,
>>
>>Considering the discussions about the FileWritingTransformer, Cocoon
>>symetry and Stefano's source/drain RT, I added in
>>org.apache.cocoon.environment a new interface I already talked about :
>>WriteableSour
At 12:02 pm +0100 25/2/02, Michael Hartle wrote:
>Michael Hartle wrote:
>
>> BTW, two aspects: first of all, I find the naming of WriteableSource
>> somehow confusing; what about
>> seperating this into Source and Drain/Sink/whatsoever and changing the
>> "src" attribute into a "dest"-attribute
>>
Michael Hartle wrote:
> BTW, two aspects: first of all, I find the naming of WriteableSource
> somehow confusing; what about
> seperating this into Source and Drain/Sink/whatsoever and changing the
> "src" attribute into a "dest"-attribute
> so this makes more sense and prevents accidential dam
Jeremy Quinn wrote:
>While working on WritableSourceTransformer, I was going to look at making a
>SourceIOTransformer, that would have two verbs :
>
>
>
>
>
>What do you guys think about this?
>This is kind of the logical conclusion to the symmetry provided by the new
>WritableSourc
At 12:22 am +0100 23/2/02, Sylvain Wallez wrote:
>The door is now open to other implementations that will allow us to
>write anything anywhere just as Source already allows to read anything
>anywhere. Some possible implementations include xmldb (Gianugo ?), SQL
>blobs, http/ftp upload, etc.
While
At 12:22 am +0100 23/2/02, Sylvain Wallez wrote:
>Jeremy, I also quickly updated the FileWritingTransformer so that it
>uses any WriteableSource instead of just files. Could you please look at
>it ? Another update would be also to the 'serializer' parameter fully
>optional so that SAX events are s
Sylvain Wallez wrote:
> Considering the discussions about the FileWritingTransformer, Cocoon
> symetry and Stefano's source/drain RT, I added in
> org.apache.cocoon.environment a new interface I already talked about :
> WriteableSource. It adds writing methods to Source's reading abilities.
Cool
At 1:50 pm +0100 23/2/02, Stephan Michels wrote:
>On Sat, 23 Feb 2002, Jeremy Quinn wrote:
>
>> Can it do this?
>>
>> This would avoid much of the need to let the user edit XML at all, and save
>> everybody a lot of grief!
>
>#token WORD [A-Za-z]+;
>#token CR \r;
>
>#whitespace [\ \t\n]+
>
>%%
>
On Sat, 23 Feb 2002, Jeremy Quinn wrote:
> >BTW, your new slash-edit demo is really nice. By crossing this with the
> >Chaperon text parser and the "crushing userland" thread, we should
> >quickly have a Cocoon-powered weblog !
>
> Ah Ha! It works ... great news!
>
> The Chaperon text parser, c
At 12:22 am +0100 23/2/02, Sylvain Wallez wrote:
>Hi team,
>
>Considering the discussions about the FileWritingTransformer, Cocoon
>symetry and Stefano's source/drain RT, I added in
>org.apache.cocoon.environment a new interface I already talked about :
>WriteableSource. It adds writing methods to
Hi team,
Considering the discussions about the FileWritingTransformer, Cocoon
symetry and Stefano's source/drain RT, I added in
org.apache.cocoon.environment a new interface I already talked about :
WriteableSource. It adds writing methods to Source's reading abilities.
Writing can occur in two
19 matches
Mail list logo
