> > 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 suppose that we could do it either way. I was trying to suggest a route that had the least amount of changes to any existing code. There is also the question of how to defines the roles for the Fulcrum classes. That is not something that I would want to package as part of Turbine. I don't know a great deal about Avalon but it seems to be a more simplistic approach to let Fulcrum keep its own container. I could be very wrong here.... > > > > > 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 ! > We could deprecate the static accessors. I would not want to just drop them at first. > > > > > 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 ! > Please do!!!!!!!!!! > -- > 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]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
