Sylvain Wallez wrote:
...
Guys, remember the real-blocks container story? Two reasons led to the
choice of OSGi: there are existing implementations, and it stopped the
endless discussions about what the container API should be.
We have exactly the same here. "why not this or that" and "I don't
need it but you can implement it" lead nowhere. NIH syndrome at work.
Cocoon's goal is not about containers, but about components. Cocoon
was one of the first component-oriented frameworks, but times have
changed!
+1000
what's wrong with the Spring bridge?
Nothing, but it currently doesn't help migrating the core and the blocks
to a modern container. For that we need to make the bridge available at
the block level, and connect it to "inter block" component management.
/Daniel
