You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Berin Loritsch <bl...@infoplanning.com> on 2000/07/12 19:52:27 UTC
Re: SAXParse error (cant find the file) when parsing stylesheets
withcocoon
"Edwards, Jayme" wrote:
>
> I updated a project that uses cocoon to use Xerces 1.1.2 and I get the following error
> whenever I try to browse XML documents that have the <?xml-stylesheet and <?cocoon-process
> tags (these used to perform the transformation without a problem). It almost looks like a pathing
> problem in the source for Xerces???
>
> org.xml.sax.SAXParseException: File "D:/projects/<directory-name-omitted>/index.xml" not found.
>
> Note <directory-name-omitted> was added by me and not returned by cocoon.
>
> Jayme
I get the same error!
I thought it was my configuration. Try down-grading to 1.1.1 and see if
that changes anything.
I get the same error regardless of Cocoon 1 or Cocoon 2.
But all the configuration files load and parse OK. Anyone know what's going on?
Re: SAXParse error (cant find the file) when parsing stylesheets
withcocoon
Posted by Berin Loritsch <bl...@infoplanning.com>.
Berin Loritsch wrote:
>
> "Edwards, Jayme" wrote:
> >
> > I updated a project that uses cocoon to use Xerces 1.1.2 and I get the following error
> > whenever I try to browse XML documents that have the <?xml-stylesheet and <?cocoon-process
> > tags (these used to perform the transformation without a problem). It almost looks like a pathing
> > problem in the source for Xerces???
> >
> > org.xml.sax.SAXParseException: File "D:/projects/<directory-name-omitted>/index.xml" not found.
> >
> > Note <directory-name-omitted> was added by me and not returned by cocoon.
> >
> > Jayme
>
> I get the same error!
> I thought it was my configuration. Try down-grading to 1.1.1 and see if
> that changes anything.
>
> I get the same error regardless of Cocoon 1 or Cocoon 2.
>
> But all the configuration files load and parse OK. Anyone know what's going on?
In Cocoon2, it appends
<!-- PATH_INFO="null" -->
to the file. Is this related? if the PATH_INFO is always null when it gets
to Xerces, of course we will have problems.