Re: C1.8.1-dev installation problem (1.8 running fine!)

[Rick Tessner <ri...@dingle.myra.com>]

On Mon, 04 Dec 2000 11:06:34 PST, Rick Tessner wrote:

>Hello All!
>
>I've been running Cocoon 1.8 (under Solaris 2.6, Resin 1.2.0 JDK 1.2.2)
>with no problems whatsoever.
>
>Today, I thot I'd take a look at 1.8.1-dev and ran into the following:
>                                                                              
> 
> Publishing Engine could not be initialized.
>
>  java.lang.RuntimeException: Error loading logicsheet at
>  resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl
>  due to java.lang.Exception: Resource not found or retrieving error.

I'm getting closer on this one. I've got 1.8.1-dev up and running, but
not quite the way I'd like under Resin.

After looking at XSPProcessor.java I found that it seems to be determining
the classpath by first querying the current servlet context by doing a 

   this.servletContext.getAttribute("org.apache.catalina.jsp_classpath");
or
   this.servletContext.getAttribute("org.apache.tomcat.jsp_classpath");

If neither of those returns anything useful, it uses the system classpath.

Ah-Ha, says I!  I try just setting the system classpath with all the
jars in my cocoon-dev/WEB-INF/lib/ directory and that works just fine.

I'm not a big fan of using the global system classpath for something like
this.  It looks like this should NOT be an issue with tomcat/catalina
since XSPProcessor.java "knows" how to find the servlet classpath.

Does anyone out there know the equivalent servletContext.getAttribute()
for Resin?  Or better, is there a standard Attribute that can be used
to get the current servlet's classpath??

-- 
Rick Tessner	rick@myra.com
MYRA Systems Corp. Fone: (250) 381 1335 x125  Phax: (250) 381 1304
                   Cell: (250) 885 9452

"Hmmm.  They have the Internet on computers now!"