On Thu, 2007-10-25 at 18:28 +0200, Reinhard Poetz wrote: > Vadim Gritsenko wrote: > > Grzegorz Kossakowski wrote: > >> Vadim, have you seen our whiteboard with the list of things people > >> have been wondering about when it > >> came to deprecation? > > > > Seen it but I would not be able to recall it. > > > > I remember though that it was acknowledged that some of the stuff > > written on the sheet of deprecated things really had no substitutes or > > migration path towards 'new stuff'. Which only means that either it was > > on the list by mistake or because 'new stuff' is half baked at the moment.
A little bit out of context maybe but one thing on deprecation I really do not like in e.g. java classes is that the method which is deprecated does not contain a hint to the new method to use. Right now cocoon-2.2 is kind of doing this ATM. For someone that used 2.1 before and is now diving into 2.2, things like how to write a component that is based on 100% spring and not Avalon are deprecation with no hints. * Are there examples for new components? * Where can we find them? * ... Deprecation with no substitutes will cause a lot of confusion. just my 2 cents salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
