On Fri, 2002-09-27 at 12:47, Vjeran Marcinko wrote: > Hi. > I've read 'developing with Apache Avalon' and stated to use ECM since it's > the container described there. I am satisfied with it, but I have some questions >though : > 1. This question will probably sound stupid - I understand that ECM controls > lifecycle of a component, but when is it supose to call methods from > Re* interfaces (such as reconfigure(), recompose() etc..) ? Does > component itself calls these methods ?
the Re* interfaces were never completely defined properly by contract. No container (and that includes ECM) provides support for them. When we get around to defining and implementing these, the container will be responsible for calling these methods. Until then, you could call these methods from another component, but I recommend you don't go down that road. For one it might break compatibility with future avalon containers, but more importantly it leads to a messy architecture. :( Sorry for the lack of clarity here. > 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. > 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... regards, Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
