Well, thanks for the advice everyone!
I think I added in the paranoid block okay by setting this in my
local.blocks.properties file:
include.block.paranoid=true
(I then cleaned and recompiled, of course)
When I loaded up Tomcat I noticed this in the localhost_log file:
2006-01-26 14:03:24 WebappLoader[/cocoon]: Deploy JAR
/WEB-INF/lib/cocoon-paranoid-block.jar to
/var/tomcat4/webapps/cocoon/WEB-INF/lib/cocoon-paranoid-block.jar
So it appears that Tomcat is loading the paranoid block, but is there
something I need to do to get Cocoon to use it? I'm still getting the
same error I was getting before when I didn't have the Xerces and Xalan
libraries in the $TOMCAT_HOME/common/endorsed directory.
In case it helps, that error was:
org.quartz.SchedulerException: Scheduler with name 'Cocoon' already exists.
Thoughts anyone?
Thanks again!
Brian
Antonio Gallardo wrote:
Brian Maddy wrote:
Hello,
According to the page
http://cocoon.apache.org/2.1/installing/index.html, Cocoon requires
some Xerces and Xalan libraries to be placed in the
$TOMCAT_HOME/common/endorsed directory. I don't believe our hosting
provider provides us with access to this directory, so is there any
way around this requirement? Couldn't I somehow include those
libraries inside my cocoon.war file?
Use the paranoid cocoon block.
Does anyone know, is it still a requirement to do this if we were
using Tomcat 5.0 or 5.5?
It depends of the cocoon version.
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
