Grzegorz Kossakowski wrote:
Yep, I haven't mentioned these sitemap-specific containers because they
are only there for back-compatibility and they are very likely to be
deprecated in the future. Moreover, these sitemap-specific containers
support only Avalon components and not Spring beans.
No, they support both :)
Carsten
As for now I advise to put beans configurations into
META-INF/cocoon/spring/*.xml and declare dependencies between blocks
that reflect dependencies between beans. This should be enough for any
future invention that will guarantee true isolation between blocks.
The other approach is the 2.1.x compatible approach: by creating a
hierarchy of sitemaps (using map:mount) you create a hierarchy of
containers (like it was in 2.1.x). It is possible to define beans on
er per sitemap base. However, it seems that current development of
Cocoon favours the blocks concept.
Exactly.
--
Carsten Ziegeler
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
