cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Engelhart <>
Subject Re: OS X & C2
Date Thu, 14 Dec 2000 15:49:20 GMT
Thanks Stuart and dims.  For whatever reason the alias/symbolic link that Mac OS X uses for
it's classes.jar file doesn't work. When I did:

setenv CLASSPATH /System/Library/Frameworks/JavaVM.framework/Versions/1.2/Classes/classes.jar
setenv JAVA_HOME /usr

all worked perfectly well. 


On Thursday, December 14, 2000, at 02:45 AM, Stuart Roebuck wrote:

> We're working with C2 under MacOS X and have progress worked through from C1 T3 through
> our current C2 T4 configuration.  I've never tried C2 and T3. 
> I'm probably stating things you already know, but it appears from your stackdump that
> first "Language Exception" is because the sitemap is not being compiled (and therefore

> can't be found in its compiled form.  The second stack indicates that the java compiler

> isn't being found in the classpath - explaining why the sitemap isn't getting compiled.
> These issues both relate to to Cocoon's processing rather than Tomcat.  So it looks like

> Cocoon can't find javac, but Tomcat can. 
> Could it be something to do with environmental variables - your "JAVA_HOME" setting or

> your cocoon.xconf configuration file? 
> I hope it is a little bit of a relief to you to know that there isn't any fundamental
reason for 
> Cocoon 2 not working under MacOS X. 

View raw message