Carsten Ziegeler wrote:
Daniel Fagerstrom schrieb:
At some point in time, e.g. now ;) we need to decide that we go for
OSGi. Keeping all roads open at all time means that we just reinvent
whats allready is standardized in OSGi.
For functionality that we allready have, we must of course respect back
compability and write wrappers beween what we have and the new OSGi
based implementations. But for new functionallity I think that we should
reuse as much as possible of what allready is in OSGi.
I think we should use OSGi *just* for the "core blocks" implementation
which is class loading, versioning and installation and that's it.
But that's just my opinion.
+1
I'd even say that at this point in time, none of the existing blocks should be
aware of OSGi existence but only Cocoon "Kernel", which uses OSGi to manage
(load/unload) blocks on the fly.
Vadim
