Cocoon 1.8.2 and Tomcat 4.1.12

2002-11-04 Thread Greg Jewell
in Cocoon 1.8.2 and Tomcat 4.1.12 appear to be incompatible with each other.) I can load cocoon/Cocoon.xml without problems. When I try to open cocoon/samples/index.xml, though, I get the following error: java.net.MalformedURLException: unknown protocol: d I've placed all the cocoon jar files

Re: Cocoon 1.8.2 and Tomcat 4.1.12

2002-11-04 Thread Joerg Heinicke
that I don't understand. In order to get this far, I've had to configure Cocoon to use the SunXMLParser rather than Xerces. (The versions of Xerces found in Cocoon 1.8.2 and Tomcat 4.1.12 appear to be incompatible with each other.) I can load cocoon/Cocoon.xml without problems. When I try to open

Re: Cocoon 1.8.2 and Tomcat 4.1.12

2002-11-04 Thread mercuron
. I've made significant progress, but am encountering an error that I don't understand. In order to get this far, I've had to configure Cocoon to use the SunXMLParser rather than Xerces. (The versions of Xerces found in Cocoon 1.8.2 and Tomcat 4.1.12 appear to be incompatible with each

FW: Cocoon 1.8.2 and Tomcat 4.1.12

2002-11-04 Thread Greg Jewell
Heinicke [mailto:joerg.heinicke;gmx.de] Sent: Monday, November 04, 2002 10:39 AM To: [EMAIL PROTECTED] Subject: Re: Cocoon 1.8.2 and Tomcat 4.1.12 Hello Greg, is there anyway written a reference to a file on drive D:\? There must be written file://D:/... instead. Regards, Joerg Greg Jewell wrote

FW: Cocoon 1.8.2 and Tomcat 4.1.12

2002-11-04 Thread Greg Jewell
: Cocoon 1.8.2 and Tomcat 4.1.12 Hi Greg, I had a similar problem under Win2k. I had to reinstall Tomcat in a directory without spaces in its path name. I do not know where the problem comes from, but I never had the problem with Tomcat 4.0. Marco Hi All, I'm trying to get Cocoon 1.8.2 up

Re: FW: Cocoon 1.8.2 and Tomcat 4.1.12

2002-11-04 Thread Joerg Heinicke
[mailto:joerg.heinicke;gmx.de] Sent: Monday, November 04, 2002 10:39 AM To: [EMAIL PROTECTED] Subject: Re: Cocoon 1.8.2 and Tomcat 4.1.12 Hello Greg, is there anyway written a reference to a file on drive D:\? There must be written file://D:/... instead. Regards, Joerg Greg Jewell wrote