All,
included is a patch that allows one to specify a root component manager for
Cocoon.
By putting
<init-param>
<param-name>parent-component-manager</param-name>
<param-value>org.apache.cocoon.components.ParentComponentManager/InitParamet
er</param-value>
</init-param>
into the web.xml, the following will happen via reflection:
ComponentManager cm = new
org.apache.cocoon.components.ParentComponentManager("InitParameter");
and then cm will be used as the parent CM of Cocoon's CM.
Of course, the class name and parameter is chosen by the user.
So, for example, to use a component manager via JNDI:
<init-param>
<param-name>parent-component-manager</param-name>
<param-value>my.JNDIComponentManager//my/namespace/ComponentManager</param-v
alue>
</init-param>
which will instatiate my.JNDIComponentManager like this:
my.JNDIComponentManager("/my/namespace/ComponentManager");
and use it as the parent CM for cocoon.
/LS
CocoonServlet.java.diff
web.xml.diff
Cocoon.java.diff
ParentComponentManager.java
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
