Carsten Ziegeler schrieb: > Daniel Fagerstrom schrieb: > >> For your questions about creating Core and Settings I use a >> o.a.c.servlet.CoreUtil from cocoon-core that has reduced functionality >> and flexibility compared to the ordinary one, it just use the servlet >> config as input. It is used within the ECMBlocksServiceManager. >> > Ok, can we try to use the same code (= same CoreUtil); I think this > would avoid duplicate efforts. I cleaned up the core CoreUtil a little > bit and the BootstrapEnvironment interface got a lot smaller; I think I > can get away with most of the other methods there as well, leaving just > some configuration hooks. And this would then make the > BootstrapEnvironment optional. So you could just invoke the CoreUtil > with a o.a.c.environment.Context object (which inherits from > ServletContext). Would this work for you? > The BootstrapEnvironment is now optional and all you need is a o.a.c.e.Context object for the CoreUtil.
I'm also wondering if we can remove the Core object as we could imho provide the whole functionality through the BeanFactory. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
