Carsten Ziegeler wrote:
Now I think that per sitemap configuration and even per sitemap class
loading are key features of 2.2. I see no need to deprecate them or
something like this.
With Cocoon 3.0 and applications that are really split into blocks, we should
only support one way of application modularization and I agree with Daniel that
this should be at the block level. But things like this don't need to be decided
today.
With 2.2 you include your component configs from
the sitemap and you define your classpath in the sitemap. With real
blocks there are only minimal changes as you just have to remove the
include and the classpath definition from your sitemap and but these
somewhere in the block config - and that's it. Your configuration of
your components stays the same.
right except that each block already has it's own classloader (remember, OSGi
;-) ...).
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
