When Turbine finally gets up to using Merlin (soon!) then we will start cutting the 1.0 release of various fulcrum components, and at that point we will make the decision of whether to remove the ROLE value from the api. Or, we may cut the 1.0 with ROLE, and then deprecate it.
For moving forward, basically, while ROLE is handy, don't use it, use the classname, because when you adopt merlin, you won't use ROLE anyway. Eric > -----Original Message----- > From: Stephen McConnell [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 18, 2004 7:50 AM > To: Avalon framework users > Subject: Re: Roles and Components in Merlin : another newbie > > > Sonu Vijay wrote: > > > Ok, that makes sense. But why do Roles still exist in > > API classes/Interfaces. I mean the code > > > > String ROLE = PoolService.class.getName(); > > > Legacy from long ago. It was required by the ECM container. > It is not > and will not be required or referenced by Merlin. Its still there in > the Fulcrum code because its part of a interface contract so > chances are > that someone that is referencing it as a shortcut to > PoolService.class.getName(). > > Stephen. > > -- > > |------------------------------------------------| > | Magic by Merlin | > | Production by Avalon | > | | > | http://avalon.apache.org/merlin | > | http://dpml.net/merlin/distributions/latest | > |------------------------------------------------| > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
