Mark,
Did you by chance play with the order of the jar files that contain
parsers? I may be way off, but I found moving the xml-apis.jar and
xerxes.jar to the top of the classpath sometimes solves parser not found
problems. Especially, when your dealing with WebSphere.
Also check to see if you have the right jars.
-Adam
"Mark Gaither"
<mark@markgaither To: <[EMAIL PROTECTED]>
.com> cc:
Subject: Re: cocoon as commandline
tool
06/11/02 02:40 PM
Please respond to
cocoon-users
----- Original Message -----
From: "leo leonid" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 11, 2002 7:42 AM
Subject: Re: cocoon as commandline tool
>
> On Tuesday, June 11, 2002, at 01:26 Uhr, Renzo Kottmann wrote:
> >
> > May someone give me a detailed discription of the URL or URI (I just
> > don't know)? Because everytime I do this:
> >
> >
>
> maybe this will help you:
>
> java org.apache.cocoon.Main -c<sourcepath> -d<resultpath> -w<tmppath> \
> -l<logfilename> -uINFO -f<list.uris>
What does your classpath environment look like? I am getting errors:
Exception in thread "main" javax.xml.parsers.FactoryConfigurationError:
Provider
for javax.xml.parsers.SAXparserfactory cannot be found
Thanks,
Mark Gaither
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
