Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [vote] Why did SourceWritingTransformer move?
Date: Fri, 17 May 2002 09:23:32 +0200
Message-ID: <GMEBIBHGAOFGJCDPJANDEEKDEFAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
Importance: Normal
In-Reply-To: <3CE18771.7060806@apache.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"

Hey,

I'm back :) and trying to get up-to-date...

> 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.
>
Yupp.

> So, I vote to place it there and change the rest accordingly
>
> Place your vote.
>
+1, but...

it's currently not possible... :)

I merged the InsertTransformer from our sunShine donation with the
SourceWritingTransformer
as they both have the same purpose. The SWT writes "complete" sources and
the InsertTransformer can insert data into an XML source via an XPath
expression.

Unfortunately the InsertTransformer uses some code of the webapps.session.*
code,
so it can't be moved without breaking functionality.
I added this to the todo list - if it's finished we can and should move it.

Carsten


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