First, let me reply saying that the Cocoon docs suck. You'll find everybody here agreeing with me, but very little ones bothered enough to change something about it.
That's why I'm doing "Forrest": current infrastructure is too rigid. At the same time, this is not an excuse not to have precise information in the docs that we already have. Scott Lamb wrote: > > I have a few minor complaints & suggestions about the installation > documentation, specifically concerning the X11/headless AWT problem. > (Sorry if this is in the wrong place. Wasn't sure if I should post this to > here or cocoon-users) Complains and suggestions go here. Questions about use go there. In short: cocoon-users is when you don't understand, cocoon-dev when you have understood enough to know there is something to fix. > Apparently, AWT is only needed by batik. Correct. > This page <http://xml.apache.org/cocoon/installing/jars.html> says that batik > is not required by core cocoon. Correct. > I took that to mean I could just download and > deploy cocoon.war file without worrying about AWT. Ah, well, that's not the case since "cocoon.war" != "cocoon.jar" (which is what we call Cocoon core) > But apparently batik is > needed to compile the sitemap now? (That's what the error lead me to > believe.) This because you probably have listed some batik-using components in your sitemap (the default one has "svg2jpg" and "svg2png". It should be enough to comment those out and the sitemap should compile with no problems. If not, there's a bug. > Is this webpage out of date? No, we need to specify better that "Cocoon.war" != "Cocoon.jar" > Maybe I could have gotten Cocoon to > work without batik by taking it out of the WEB-INF/lib dir and/or changing > the sitemap.xmap but Cocoon definitely wanted it by default. Ok, what is your suggestion on how to fix this? > This page <http://xml.apache.org/cocoon/faq.html#faq-24> says that an X11 > server is required to make AWT/batik happy, but another page > <http://xml.apache.org/cocoon/installing/index.html> suggests just > replacing Java's AWT with PJA. JDK 1.4 beta's AWT also doesn't require an > X11 server, though apparently you need to recompile bits of Cocoon to use > it. Really? didn't know that. I tried JDK 1.4 and didn't give problems to old java programs of mine, but I was testing mousewheel support in Swing and therefore didn't run Cocoon. Do you have more info on this? > I think these should be on the FAQ page, since Xvfb seems much more > awkward than having a true headless AWT. Good point. I agree, this should be a big FAQ. It was also proposed to comment out the Batik serializers from shipped 'cocoon.war' to avoid those problems and I agree this is a good solution. But we need also to explain what we did and why otherwise people will never use Batik on the server. > Also, I don't think the installation guide's PJA directions are quite > right. I followed PJA's instructions and ended up with something more like > this: > > $ export CATALINA_OPTS="$CATALINA_OPTS \ > -Xbootclasspath/a:$JAVA_HOME/jre/lib/ext/pja.jar \ > -Dawt.toolkit=com.eteks.awt.PJAToolkit \ > -Djava.awt.graphicsenv=com.eteks.java2d.PJAGraphicsEnvironment \ > -Djava2d.font.usePlatformFont=false \ > -Djava.awt.fonts=$JAVA_HOME/jre/lib/fonts/" > > which is a bit different. It didn't work for me without the > -Xbootclasspath, no matter where I put the jar. And the PJA docs were > pretty specific about that; they said that adding it to $CLASSPATH wasn't > enough. Maybe these instructions should be changed or (especially if PJA's > installation procedure changes a lot) just replaced by links to PJA's > install instructions. Hmmm, don't know about this... I never used PJA so I don't know what to say. Anybody? -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. <[EMAIL PROTECTED]> Friedrich Nietzsche -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
