cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ricardo Rocha <rica...@apache.org>
Subject Re: XSP Problem, FreeBSD, java.io.IOException
Date Thu, 27 Apr 2000 21:06:21 GMT
On Mon, 02 Jun 2036, Joseph Frazee wrote:
> I'm having a problem running XSP on FreeBSD 3.4 w/ Apache 1.3.12 w/ JServ 1.1
> w/ Cocoon 1.7.2.
> 
> java.io.IOException: bad path error
> at java.io.File.getCanonicalPath(File.java)
> at org.apache.cocoon.processor.xsp.XSPProcessor.process(XSPProcessor.java)
> at org.apache.cocoon.Engine.handle(Engine.java)
> at org.apache.cocoon.Cocoon.service(Cocoon.java)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
> at org.apache.jserv.JServConnection.processRequest(JServConnection.java:314)
> at org.apache.jserv.JServConnection.run(JServConnection.java:188)
> at java.lang.Thread.run(Thread.java)

The XSPProcessor uses getCanonicalPath to determine the "real" location of
the source XML document so that 2 or more links to the same physical file
result in a single Java class being generated and cached.

Apparently, this strategy may pose a problem in certain setups (bad path error).

A possible workaound is to use getAbsolutePath() whenever getCanonicalPath()
throws an IOException, though this may impair the advantage of having a single
Java class per physical file...

What's your XSP document's filename? If it's a [symbolic] link to another
location, are you sure you have read/execute access to all directories in its
path?

Ricardo

Mime
View raw message