On Friday, September 27, 2002, at 07:54 AM, Leo Simons wrote: >> 2. Is ECM to be updated with new ....service.* package instead >> ...component.* ? > > no. A next-generation container called Fortress is intended to replace > ECM in the future; it provides support for service.*. Migration from > ECM > to fortress should be totally painless. > Work is currently in progress on creating a fortress release.
ECM supports hosting components that are Serviceable. If you want to have a nested hierarchy of ECM instances, you must use Components as the ECM only supports having parent ComponentManagers, not ServiceManagers. >> 3. Is LogKit the only type of logger allowed to be passed to ECM ? >> (I prefer using JDK 1.4 logger since I have it already in JDK...) > > I can honestly say I don't know (never tried). Someone else will have > to > answer that one... ECM supports the org.apache.avalon.framework.logger.* abstraction, which includes a Jdk14Logger. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>