cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: problem solved!
Date Thu, 14 Mar 2002 09:54:53 GMT
[forgot to cc the list...]

-------- Original Message --------
Subject: Re: problem solved!
Date: Thu, 14 Mar 2002 10:16:52 +0100
From: Sylvain Wallez <>
To: Ovidiu Predescu <>
References: <>

Ovidiu Predescu wrote:

 >I found where the problem was! I forgot to declare one of the
 >components I was adding to my ComponentSelector as implementing
 >Component, and the error message was somehow lost.
 >Everything works fine now, so please disregard the earlier messages.


However, here are some brief explanations of all the component managers
(CM) : every Processor instance has its own CM. For example, components
created in a subsitemap are handled by this subsitemap's CM, whose
parent is the root sitemap's CM, whose parent is the main Cocoon CM.

The local CM of a sitemap is configured with the contents of
<map:components> and also inherits all components defined in its parent CM.

And because every Processor language can need new roles that don't exist
in the main roles definition file, there's a <roles> section in the
definition of a language that is used to create RoleManager associated
to the local CM.

This role management allowed roles for MatcherSelector,
GeneratorSelector, etc. to be defined only for the sitemap language
without having to be declared in the top level role definitions. This
was really usefull until we decided to move some of the most commonly
used sitemap components in cocoon.xconf, which also required to move the
assiociated roles. But the feature is here if needed.

I'll formalize all this soon.


Sylvain Wallez
   Anyware Technologies                  Apache Cocoon 

To unsubscribe, e-mail:
For additional commands, email:

View raw message