You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by Bertrand Delacretaz <bd...@codeconsult.ch> on 2003/04/29 09:39:00 UTC

Re: Continous Integration

Le Mercredi, 30 avr 2003, à 00:33 Europe/Zurich, Niclas Hedhman a écrit 
:

> ...I should be
> able to "repoint" the "project directory" accordingly, preferably not 
> inside
> the Cocoon "product directory".

I agree that this would be useful. Most probably the sitemap is 
currently accessed through the ServletContext, implying some 
limitations, but I haven't looked at the code.

There are probably security issues in allowing Cocoon to access stuff 
outside of the servlet context, but if this "project directory" is set 
by a system property or startup parameter it could be safe I think.

> ...The "project directory" should also allow a "./lib/" directory for 
> my own
> code, and get loaded without any special configuration.

Yes, lib, sitemap.xmap, .xconf files as well?

I like the general idea - having cocoon act on a "work directory" that 
is outside of the Cocoon filesystem tree.

<snip-other-good-ideas/>

-Bertrand

Re: Continous Integration

Posted by Niclas Hedhman <ni...@hedhman.org>.

On Monday 28 April 2003 11:39 pm, Bertrand Delacretaz wrote:
> Le Mercredi, 30 avr 2003, à 00:33 Europe/Zurich, Niclas Hedhman a écrit
> There are probably security issues in allowing Cocoon to access stuff
> outside of the servlet context, but if this "project directory" is set
> by a system property or startup parameter it could be safe I think.

Better yet, proper usage of java.security.manager. That's why it exists.

Niclas