giacomo wrote:
>
> On Thu, 19 Jul 2001, Michael McKibben wrote:
>
> > I am new to cocoon and have been playing with the beta1 for several days
> > now. I am salivating over all the possibilities available with cocoon2!
> >
> > One issue with the Cocoon Servlet: it seems unsafe to assume that the
> > WEB-INF/ directory is writeable by the Servlet (or for that matter, anything
> > inside the Servlet context!). What if the Servlet container serves
> > everything directly out of the WAR file? It seems a safer approach would be
> > to take advantage of the ServletContext attribute:
> > "javax.servlet.context.tempdir" (Servlet Spec, 4.7). This attribute is of
> > type java.io.File, and can be used as the base directory for the workdir.
> > This method should work even if the Servlet container is using a more
> > restrictive java policy.
>
> Yes, I knew this will come sooner or later. If a servlet container is
> not expanding the war file (which Tomcat can do as well IIRC) we have a
> problem with the logger and the hqsqldb.
>
> What do others think about it? Is the workdie the right place to go for
> such fs activity?
I thought of that--but different vendors place the work directory in
unpredictable places. For HSQL--it would be better for people to install
it correctly. Anyhow, it's not a nice subject...
S/MIME Cryptographic Signature
