cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <>
Subject Re: [vote] Why did SourceWritingTransformer move?
Date Thu, 16 May 2002 09:14:25 GMT

On Tuesday, May 14, 2002, at 10:53  pm, Stefano Mazzocchi wrote:

> Today I was looking for SourceWritingTransformer in HEAD but 
> couldn't find it anymore, so I did a big grep and found it on
>  org.apache.cocoon.webapps.session.transformation
> I totally understand that this might be very useful in those 
> cocoon.webapps locations (which awefully start looking like 
> cocoon blocks to me... gosh, I with I had time to implement 
> those damn blocks!), but I think it's general enough to go into 
> the usual
>  org.apache.cocoon.transformation
> At least, I found many very nice uses of it.
> So, I vote to place it there and change the rest accordingly
> Place your vote.


However, I believe we still have a problem with this code when 
used in certain ways ......

We had reports a while ago that when you make a pipeline that 
first reads a Source in, modifies it, then writes the Source 
back out to the same location using SourceWritingTransformer, 
the write gets blocked by the read (which is still possibly in 

This problem has not arisen in the current incarnation of 
<slash-edit/> because I am always making the modified Source 
from scratch, not after having read it in first.

I would love to know what is going wrong here, but am still 
unable to work on this stuff due to other commitments.

regards Jeremy

To unsubscribe, e-mail:
For additional commands, email:

View raw message