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.
can't you get around this with the <load-on-startup> directive in web.xml ?
IIRC if you put the cocoon servlet as 2 and your config servlet as 1 then the servlet container will load your config before cocoon (don't know if this is guaranteed behaviour though - look into your container docs)
Jorg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
