Bertrand Delacretaz wrote: >On Thursday 11 July 2002 22:44, Andrew C. Oliver wrote: > > >>. . . >>I'd like to propose we remove the SQLTransformer from Cocoon 2.1 and >>newer releases, remove all SQLTransformer based samples (or provide esql >>alternatives). >> >> > >(I have no formal voting rights here but) >-1 > >Why remove a component that works? >This would certainly break some existing apps and annoy users. > >Maybe it could be marked "deprecated", as is done in java, meaning it won't >be developed any further and is not recommended for new projects. > > > And that has worked so well in Java.... hehe. Its been deprecated for awhile. The documentation has said this. Officially Sun considers deprecated to mean that in future releases it may go away. They're just lazy about doing it. This results in some things that work intermittantly which is the worst kind of bug.
One reason is that its a maintenance drag, cocoon is undergoing some resonable re-engineering under the covers, along with Avalon. Updating this deprecated class is a drag. As an alternative, perhaps we could move it off into something like the scratchpad like a "oldstuff" or "compatibility-layer" kinda deal so that it isn't included by default. Thoughts? -Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
