> From: Sylvain Wallez [mailto:[EMAIL PROTECTED]] > > Bertrand Delacretaz wrote: > > >On Tuesday 05 March 2002 09:21, Torsten Curdt wrote: > > > >>. . . > >>We should be able to have a separate configuration besides the > >>configuration for the core components. We should be able to define a > >>user.xconf. (or better user-components.xconf?) > >>. . . > >> > > > >From a user's point of view, being able to drop the .xconf and required > >jars in a directory under mount/ would IMHO be a great first step > >towards "pluggable cocoon apps": > > > >mount/my-app > > sitemap.xmap > > cocoon-config/my-components.jar > > cocoon-config/my-jdbc-driver.jar > > cocoon-config/my-app.xconf > > docs/index.xml > > . . . > > > >Currently this mount thing works great (even without stopping cocoon) > >if you need just a sitemap and content files, but as you mention more > >than that needs editing the global cocoon.xconf and/or copying jars > >under WEB-INF. > > > In the interpreted sitemap engine, the <map:components> section is > handled as regular component manager configuration (i.e. a .xconf file), > so you can add any component you wish in it.
I have got two questions... 1. Should this be implemented in the interpreted sitemap as well? 2. Do we need separate user.xconf then, if you can do everything in the sitemap? Vadim > The only piece that's missing is a classloader per subsitemap to load > additionnal jars. But we should be careful with that since this places > code in areas that are potentially visible from the client browser (the > servlet engine hides the contents of WEB-INF). A solution could be for > the sitemap engine (or Cocoon itself ?) to forbid access to all URIs > containing 'WEB-INF/'. > > Thoughts ? > > Sylvain > > -- > Sylvain Wallez > Anyware Technologies Apache Cocoon > http://www.anyware-tech.com mailto:[EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
