You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Donald <do...@apache.org> on 2001/03/15 07:11:44 UTC

Component*Exception

Hi,

I was just about to go and deprecate the ComponentNot*Exception and came
across something. The proposal changed ComponentManagerException to
ComponentException presumably because it was used in places like
ComponentSelector. So instead of doing deprecation now - how about we
deprecate the lot and move to ComponentException? I can fix up the
avalon/james codebases within about 10 minutes and the old classes would
still be around deprecated. I just want to avoid deprecating something now
- only for it to change again in Avalon4.0.

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*


---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org