On Sun, 2003-01-26 at 16:20, Quinton McCombs wrote: > I would like to propose that we drop stop using the strutum lifecyle > interfaces altogether in favor of Avalon's interfaces.
+++++1 > > Fulcrum currently has it's own ECM that is used load load it's services. > This can still remain in place. When a service is loaded from within > Turbine, the request would go to Turbine's instance of the ECM. If > there is no component loaded with Turbine's ECM that matched the role, > the request would be passed to Fulcrum's ECM. Why not use only one container ? > > I think that this can be done without affecting the way that services > are used within Turbine. We can still keep the abstract classes with > static methods that we have in place right now. They will simply pass > the request to obtain a reference to the service to Turbine's ECM. I think this static accessor should be dropped ! We should use component composition instead ! > > The next issue is that of logging. Although ECM 4.1 will not make use > of log4j, the latest development version does appear to do so. I have > played around with this a little but I don't have that working yet. I have a LoggerFactory component to use, instead of subclassing AbstractLogEnabled, but it uses Log4j interfaces and not commons-logging. The change from log4j -> commons-logging is in my todo list for a while now. If its decided that a logger component should be used , I will change my component to be used inside turbine ! -- Leandro Rodrigo Saad Cruz IT - Inter Business Tecnologia e Servicos (IB) http://www.ibnetwork.com.br http://jakarta.apache.org/ojb -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
