On Thursday 25 April 2002 01:52 am, Carsten Ziegeler wrote: > > If the parent CM doesn't (and isn't expected) to have the component, we > > expect a ComponentException there on the 1st lookup() since the > > ComponentHandler for the component has yet to be created. (These are > > components defined only in the roles file, not in the config). > > But a CM can throw a ComponentException in other cases as well, for > example if it catches another exception and rethrows a ComponentException.
ahh, true. I guess the question is: When should at CM atttempt to check its parent CM for the component, when it finds that it has no ComponentHandler for the component, or when it finds that it has no ComponentHandler *and* can't create the ComponentHandler itself? This would be swapping the m_parentManager and m_roles checks inside of the ECM. The only pitfall would be the case where the current CM *and* the parent CM have the ability to create the ComponentHandler, but the parent CM has managed to create it first. By swapping the two it would get created on the child before checking the parent. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
