You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Joseph Frazee <jp...@usa.net> on 2000/04/27 23:00:54 UTC
XSP Problem, FreeBSD, java.io.IOException
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.
Basically I get,
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 parsing of regular XML documents goes without a hitch. So, I doubt that
there are file permissions problems.
The only thing I can think of is that I have no tools.jar.
Help please?
Thanks,
Joseph P. Frazee
jpf3@po.cwru.edu
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
Re: XSP Problem, FreeBSD, java.io.IOException
Posted by Ricardo Rocha <ri...@apache.org>.
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
Re: XSP Problem, FreeBSD, java.io.IOException
Posted by Ricardo Rocha <ri...@apache.org>.
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