vinay nair wrote: > Hi, > While reading the "implementing the dream" chapter , > (page 37 of the pdf version) > i found a code snippet adding ComponentHandler > instance with the DefaultComponentManager . > Of what i have seen so far in the code , > ComponentHandler is not Component. > am I overlooking something in arriving at this > conclusion?
ComponentHandler is a wrapper to handle the logic of whether the Component should be accessed via Factory method, Pooled Component, or singleton (ThreadSafe). So you are right. ComponentHandler is not a Component. You use it to get your hands on one--without worrying about the details of how the Component should be managed. > With Loggable interface deprecated would be it be > advisable to make the excalibur.component.* > classes also extend AbstractLogEnabled instead > of AbstractLoggable. ? > > Maybe here too i am missing something all-together . Unfortunately, we do have to maintain backwards compatibility. There is a new package in scratchpad which will properly separate the ComponentManager interface from the Container (unlike the ExcaliburComponentManager which acts as both). That will be LogEnabled clean, and will not support Loggable components. ---------------------------------------------------- Sign Up for NetZero Platinum Today Only $9.95 per month! http://my.netzero.net/s/signup?r=platinum&refcd=PT97 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
