Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3D30283F.3020005@apache.org>
Date: Sat, 13 Jul 2002 09:16:47 -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: <LGEDIKJICGOANGDLBIJDEEAJCMAA.luca.morandini1@tin.it>
 <200207131512.09050.tcurdt@dff.st>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Torsten Curdt wrote:

>>P.S.
>>I use SQLTransformer only, and I'm happy with it :) don't deprecate it :(
>>    
>>
>
>I guess it would be cool for both ESQL and the SQLTransformer to share code as 
>well as syntax. But this will probably break backwards compatibility for 
>both. IMHO it could be nice to start a new combo of XSQL logicsheet and 
>XSQLTransformer from scratch.
>  
>
Off the top of my head this sounds good.

>We could then deprecate ESQL and SQLTransformer and only apply bugfixes. So 
>it's up to them to upgrade to the new combo syntax or keep the old stuff.
>
>How about that?
>
Sounds good to me.  But I would ask that there be a period of 
deprecation after which the old components move
out of the main build.  Let those who want to use Cocoon 2.3 with 2.0 
components do so at their own peril.  Kind of
an EOL (end of life) mode.  Otherwise to paraphrase Stefano, you hasten 
the cold death of the Cocoon universe.

-Andy

>--
>Torsten
>
>---------------------------------------------------------------------
>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