cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <ovi...@metalanguage.com>
Subject confusion about configuration files
Date Wed, 13 Mar 2002 07:01:03 GMT

Sylvain,

I'm running into problems trying to define a ComponentSelector. First
I was confused to where to put the definitions for it when I'm using
the interpreted sitemap. I always thought you need to define a role
for the component selector in cocoon.roles, then specify its
configuration in cocoon.xconf, but then there is
treeprocessor-builtins.xml (more on this later).

I've defined my component selector and registered it by creating my
own user.roles in the Web app, and then adding in the top 'cocoon'
element of my cocoon.xconf an attribute
'user-roles="/user.roles". Then I've added a .xconf snippet in my new
component, which is incorporated in the main cocoon.xconf using
XConfTool (great tool Carsten!). Using these, my component selector is
initialized just fine.

After doing these, I then went ahead to define my own extensions to
the sitemap. So I started hacking the treeprocessor-builtins.xml to
add my own builders and node handlers. I expected that once I make
these nodes Composable, they'd receive Cocoon's ComponentManager, so
the lookup of my original component selector would work fine. However
this doesn't seem to be the case: the ComponentManager received by
these nodes is a different instance! So my lookup doesn't work :-(

What is going on? Is there a better way to implement this?

Perhaps using the treeprocessor-builtins.xml? I've noticed in this
file that you make use of ComponentsSelector, when defining the normal
sitemap components. This seemed to already do the work I was
interested in, so I've tried declaring my component selector in this
file instead of the .xconf snippet (which ends up in cocoon.xconf).
No success however :-(. My component seemed to be completely
ignored. I was also confused about the meaning of the <hint> element,
as in the cases I've seen, they don't define all the components
available to a selector. Also when I removed the entry in user.roles,
my component selector was totally ignored.

I am now totally confused about which configuration file defines
what. I would appreciate if you please briefly describe what happens,
and how things work?

Best regards,
-- 
Ovidiu Predescu <ovidiu@cup.hp.com>
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message