cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Sutic" <leo.su...@inspireinfrastructure.com>
Subject RE: ParentComponentManager & config files
Date Thu, 01 Nov 2001 17:11:58 GMT
Marcus,

the ParentCM was intended to be used with JNDI. The rationale is as follows:
Component settings for the individual servlet is specified in cocoon.xconf.
Therefore, the per-servlet settings are already addressed and there is no
need for a ParentCM. However, in order to configure multiple servlets you
need to break out of the webapp context, and then JNDI is the only safe and
standard way. (There is, of course, more to the security aspects, but I
won't pretend to know it. The above was the reasons I implemented it as I
did.)

That said, the string being passed *is* a general string argument. You can
use it as you see fit. As for the resolving of paths relative to the webapp
context, currently Cocoon will only honor Loggable and Initializable
contracts, but this is not an obstacle - it would be relatively simple to
make it honor another contract as well, maybe Contextualizable (?), and pass
the servlet context.

/LS


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


Mime
View raw message