cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolás Lichtmaier <n...@technisys.com.ar>
Subject Re: XSP compilation and classpaths problems (2)
Date Thu, 25 Jan 2001 20:50:12 GMT
> To run multiple instances of Cocoon in the same virtual machine (in ??different
> zones), the ./bin/cocoon.jar file needs to be included in the zone's classpath
> (together with other zone specific classpath components). so, you need to
> properly set the ??processor.xsp.localclasspath property. This property tells
> the XSP engine wich classpath to use when calling the compiler, as there's
> ??currently no way for Cocoon to ask the classpath to the zone's ??classloader.
> The value of this property should be the classpath ??used in the "repositories"
> parameter (which includes ??cocoon.jar). Please note that the port for doing
> this is still experimental.
> 
> This is only for the latest cocoon version, right?

Yes, I faced the problem you described in the previos message and added 
the localclasspath property, and code to allow setting Cocoon properties 
in the zone's definition file.

> And I would use this as follows?: (I can't test right now
> I'm still using 1.7.4, I have to upgrade first)
> 
> zone.properties:
> 
> ...
> repositories=bla1.jar,bla2.jar
> processor.xsp.localclasspath=bla1.jar:bla2.jar
> ...
> 
> Does this look right?

Yes, please tell me if it doesn't work, since you'll be the second one 
using this feature.. =).


Mime
View raw message