Re: Fwd: cvs commit: avalon-excalibur/fortress/src/java/org/apache/avalon/fortress/impl/handler ComponentFactory.java

Sylvain Wallez <[email protected]> Wed, 19 Mar 2003 23:45:11 +0100
Newsgroups gmane.comp.jakarta.avalon.phoenix.devel,gmane.comp.jakarta.turbine.maven.devel
Organization Anyware Technologies
Message-ID <[email protected]>
Berin Loritsch wrote:

> Peter Donald wrote:
>
>>
>>   Modified:    fortress/src/java/org/apache/avalon/fortress/impl/handler
>>                         ComponentFactory.java
>>   Log:
>>   Print warning on usage of Composable
>
>
> I assume you wrote this to give us a head's up?
>
> Remember that Composable is _soft_ deprecated because of real reasons
> that our users brought up.
>
> They should not be punished because their users haven't upgraded yet.
> I would hold off on this until folks have a reason to upgrade. 


Yep. Moreover, the problem is not only in Cocoon's code base, but also 
in its user's own code.

Now I recognize that there may be a need to advertise this soft 
deprecation in a way or another. So a warning (or info ?) logged _once_ 
per VM or per classloader should be enough.

Moreover, time going on, there are more and more features or classes 
that are deprecated but kept for backwards compatibility. It would be 
good to have all these deprecation messages logged in a single category. 
A static Logger could do the trick, but this isn't a clean solution. Any 
idea about this ?

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }