> > Well technically classes should not have a ROLE string. Only interfaces > > have a ROLE and all implementations of interface share same ROLE. So > > neither ExcaliburComponentSelector nor BundleSelector should define ROLE > > IMHO. > > > :) > > So why did the author/changer of BundleSelector choose to set a > different ROLE (that's what I was looking to get an answer for)
No idea - I just made it final ;) -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
