Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-users@xml.apache.org
Message-ID: <3D8880F7.5040701@verizon.net>
Date: Wed, 18 Sep 2002 09:34:47 -0400
From: Vadim Gritsenko <vadim.gritsenko@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.1) Gecko/20020826
MIME-Version: 1.0
To: cocoon-users@xml.apache.org
Subject: Re: Cocoon 2.0.3 under Enhydra 3.1
References: <9ACCC94F3FC0C64583E2B6F8CCF04D06029C3E@postoffice.waterford.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Matthew Hailstone wrote:

>Vadim,
>  Thanks for your reply and the reference to the patch. I've been
>pulling my hair out trying to make Cocoon work under Enhydra3.1. :) I
>performed a CVS update on a previously checkedout cocoon_2_0_3_branch
>tag module. It appears to be the 2.0.4-dev version. I verified that the
>patch that you linked me to had been made in that update. I created a
>war file, extracted it to Enhydra's webapps directory, and setup the
>webapp again through the Enhydra Admin Console interface. When I try to
>run Cocoon, I get the following error page:
>
>Cocoon 2 - Internal servlet error
>
>------------------------------------------------------------------------
>--------
>
>type fatal
>
>message Cocoon was not initialized.
>
>description Cocoon was not initialized. Cannot process request.
>
>sender org.apache.cocoon.servlet.CocoonServlet
>
>source Cocoon servlet
>
>request-uri
>
>/
>
>access.log:
>  
>
...

>WARN    (2002-09-17) 16:12.52:575   [access] (Unknown-URI)
>Unknown-thread/CocoonServlet: Could not force-load class:
>org.hsqldb.jdbcDriver
>java.lang.ClassNotFoundException: org.hsqldb.jdbcDriver
>	at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>

This could have same reason as another exception below...
...

>ERROR   (2002-09-17) 16:12.52:575   [access] (Unknown-URI)
>Unknown-thread/CocoonServlet: Exception reloading
>java.lang.ClassNotFoundException: org.apache.cocoon.Cocoon
>	at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>	at java.security.AccessController.doPrivileged(Native Method)
>	at java.net.URLClassLoader.findClass(URLClassLoader.java:183)
>	at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
>	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:281)
>	at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
>	at
>org.apache.cocoon.util.ClassUtils.loadClass(ClassUtils.java:88)
>	at
>org.apache.cocoon.util.ClassUtils.newInstance(ClassUtils.java:75)
>	at
>org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:
>1221)
>

CocoonServlet can't load Cocoon class.
...


>Now, interesting to note, I'm probably doing some weird stuff. I
>followed the following procedure to get Cocoon working on Enhydra in the
>first place:
>
>http://www.mail-archive.com/cocoon-users@xml.apache.org/msg12654.html
>or
>http://enhydra.enhydra.org/project/mailingLists/enhydra/200201/msg00049.
>html
>
>We both came to the same conclusions, which made me feel like I was
>doing something right. :)
>

In the second email it was recommended to use Paranoid servlet which 
makes me to think that enhyndra has broken class loader. Issues with 
broken class loading can be endless and hard to trace.

In your install, however, you are trying to start with regular 
CocoonServlet (as far as I can tell). Have you tried paranoid servlet?


>In the above case, I'm actually using the xerces1.4.4 version from
>Cocoon 2.0.1 lib directory with the xml-apis.jar from the Cocoon
>2.0.4-dev lib directory. (The xml-apis jars from both versions didn't
>seem to make much difference.) If I use the xercesImpl-2.0.0.jar from
>the Cocoon 2.0.4-dev lib directory, I get the following errors while
>Enhydra's multiserver starts up:
>
>Enhydra$ /usr/local/enhydra3.1/bin/multiserver
>  
>
...

>2002.09.17 16:31:38: Cocoon2,ERROR: Parse failure: (class:
>org/apache/tomcat/uti
>l/XMLParser, method: parse signature:
>(Lorg/xml/sax/InputSource;Z)Lorg/apache/to
>mcat/util/XMLTree;) Incompatible object argument for function call
>

Here, Tomcat has a class which is not compatible with the latest XML 
API. Means, you won't be able to run this system with latest XML tools.

...

>I hope this gives a helpful perspective on someway that the problem can
>be fixed.
>

I hope my comments will give you perspective on possible ways of 
resolving this problem
(I'm merely helping you help yourself ;-)

Vadim


>Thanks again,
>
>Matthew
>  
>


---------------------------------------------------------------------
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:     <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail:   <cocoon-users-help@xml.apache.org>