You have written a cocoon matcher yourself? Can you delay the moment you are reading the config
file? I recall a setup function that is executed at loading, a configure that is executed at reading
(changed) sitemap and of course the match function itself. (correct me if i'm wrong, writing this
from the top of my head.) You might consider reading the config file each time a match is evaluated.
I'm not certain this will help you, but might be worth a try..
Cheers,
Geert
Rob Norman wrote:
Thanks for the quick response. I tried using
"context:/config.properties" in cocoon.xconf and that works for loading
the file directly from WEB-INF.
However, cocoon:/ doesn't work. I have a matcher in my sitemap that
matches on config.properties (I can load it from the browser using the
appropriate URL ok) but it doesn't want to work in the xconf. I'm
gussing this is because the sitemap isn't properly loaded when cocoon
reaches that part in it's initialisation. The problem is that I need to
change config files depending on what host the user is loading the page
from so I need to use the matcher.
Cheers,
Rob.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
