Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3D2E35B4.9040303@apache.org>
Date: Thu, 11 Jul 2002 21:49:40 -0400
From: "Andrew C. Oliver" <acoliver@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [PROPOSAL] Remove SQLTransformer in 2.1
References: <FCEPLAOECPOAGINFDFCHCEAKFKAA.per@onclave.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>
>
>How can that be true? The transformation point in the pipeline is very
>different than a generator. For example, I can order transformations such
>that the SQL transformer comes between other transforms but you couldn't do
>that with a generator.
>  
>
Very few times is there a reason to build your query and pass it to the 
transformation layer and I sure can't think of one.  Secondly, this
"Transformer" is an extreme violation of the contract specified for a 
Transformer.  It more fits in with what a generator does.

-Andy

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


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