On Wed, 29 Aug 2001, Matt Jezorek wrote:
> I have went to tomcat 4 b7 and the cvs version of C2 but still getting this
> error any help?
>
> message The sitemap handler's sitemap is not available. Please check
> /home/jakarta-tomcat-4.0-b7/bin/./../webapps/cocoon/WEB-INF/logs/cocoon.log
> for the exact error.
If you have an X server installed on your box, try launching tomcat from a
X session. This should *solve* the problem.
It seems the real matter is Batik using awt for svg content generation. I
had the same problem, and by searching the archives of this list (you
should have done the same), I found several solutions, some I haven't
tested yet.
The first one is using Xvfb, so cocoon use it for svg generation. Someone
on this list posted a piece of code to add to init script, I will
reproduce it here :
###########################################################
if [ "$1" = "stop" ] ; then
# kill off any framebuffer running, kill kill kill :-)
kill -TERM `/sbin/pidof Xvfb`
elif [ "$1"="start" -o "$1"="run" ] ; then
# start up a virtual framebuffer for cocoon2's rendering
Xvfb :1 -screen 0 320x240x24 &
fi
###########################################################
Do we need to add a "export DISPLAY=":1" ?
The second solution is to remove support for svg content generation from
your sitemap. I don't know if it is sufficient, I haven't tried yet ...
The comments on the list seemed to confirm this. This is probably the best
solution, if you don't need svg content generation ...
Raphael
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
