> > > ExcaliburComponentManager and friends are *not* deprecated.
> > > Using them will definitely cause deprecation warnings in
> > the interim,
> > > but that is the price to pay for backwards compatibility.
>
> The ExcaliburComponentManager will is going to be deprecated???
> I thought the standard ComponentManager should be deprecated and Phoenix was
> still using it for some reason.
> Is there a new component manager that provides roles, hints, etc ???
> I just went through great pain to use the standard ComponentManager I got
> from Phoenix only for blocks and to use the ExcaliburComponentManager for
> all the components inside the block.
>
> The ExcaliburComponentManager is used all the time in the white
> paper/tutorial "Developing With Apache Avalon". Inside this paper it is
> favored very much over the standard ComponentManager. There are two full
> pages ("Making the Configuration Pretty") only about the advantages of the
> ExcaliburComponentManager!!!
I don't know about deprecation of the ExcaliburComponentManager class
but it currently uses deprecated api for Log. Your remark illustrate
what I wrote, difficulty to use avalon due to the mixe of version (api,
recommendation, tutorial...). And I'm volontaire to help change that.
Regards,
--
--------------------------------------------------------------
David "Dwayne" Bernard Freelance Developer (Java)
mailto:[EMAIL PROTECTED]
\|/ http://dwayne.java-fan.com
--o0O @.@ O0o-------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
