This seems to me also an acceptable solution. Why is it not beautiful enough? You're just working around a cocoon "limitation" in a very simple way - to me it's a KISS certified solution.
Maybe put a configuration interface in between that abstracts the fact you're pulling values from a configuration servlet, just to beautify it ;)
Trouble is that the servlet engine creates the instance of the servlet. The getInstance() method on the ConfigurationServlet *might* return null if the servlet engine did not initialize the servlet before I request the configuration. Because I know the CocoonServlet has a lot of initialization to do before my component is launched and the ConfigurationServlet is requested to retreive the configuration it does not make it a safe sollution.
-- Ivo Limmen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
