cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Oliver <>
Subject Re: Bug 16580; compiling xsp with classpath
Date Mon, 17 Feb 2003 01:56:19 GMT
OK. Here you go. EmbeddedJavaCompiler is an implementation of 
LanguageCompiler that doesn't depend on CLASSPATH but instead uses the 
thread context class loader to load dependent classes.

I've attached a working version (minimally tested) . I've also attached 
a new version of that you'll need also. I modified it 
slightly to not rely on the AbstractJavaCompiler class but instead to 
use interfaces only. You'll also need to place javacApi.jar somewhere in 
your classpath when you compile cocoon, and you'll need to place 
javacApi.jar, javacImpl.jar, and jdtcore.jar in your classpath when you 
run cocoon. (You can get these here:

Right now, I can't commit these changes because:
1) I'm still waiting for Brian Behlendorf to change my password
2) We need to decide where to put the JavacAPI classes (other than 



Stefano Mazzocchi wrote:

> Christopher Oliver wrote:
>> Actually I am in the process of trying to do this but got immediately 
>> stopped by the below when I first tried to run cocoon (built from 
>> today's cvs),
>> Anyone care to help?
>> Regards,
>> Chris
>> ERROR   (2003-02-16) 13:12.15:159   [access] 
>> (/cocoon/documents/index.html) Thread-10/CocoonServlet: Problem with 
>> Cocoon servlet
>> org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
>> org.apache.cocoon.CascadingIOException: 
>> org.apache.xml.utils.WrappedRuntimeException: The output format must 
>> have a '{}content-handler' property!: 
>> org.apache.xml.utils.WrappedRuntimeException: The output format must 
>> have a '{}content-handler' property!
> I'm experiencing similar errors as well but I'm currently refactoring 
> things heavily on my disk so I can't really help you out until I'm 
> done (should take a few days). Then I'm glad to help you on this 
> javacapi stuff.

View raw message