cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Myers <>
Subject Re: Documentation complaints
Date Fri, 21 Dec 2001 23:51:24 GMT
i made the mess on installing/index.html.  The reason it doesn't say -Xbootclass... is because
i was too stupid to do it that way when i wrote the instructions.  They took a patch from
me that made index the mess that it is, so i am certain the committers would take a patch
from you which would clean it up.  I think the instruction should be moved to faq also.  Perhaps
you could combine the answers in that question and include info on jdk 1.4 as well.  You are
probably right about just providing a link to the pja install page.  PJA's instructions have
gotten much better since i first used it.


On Fri, Dec 21, 2001 at 12:07:54AM -0600, 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)
> Apparently, AWT is only needed by batik. This page
> <> says that batik is not
> required by core cocoon. I took that to mean I could just download and
> deploy cocoon.war file without worrying about AWT. But apparently batik is
> needed to compile the sitemap now? (That's what the error lead me to
> believe.) Is this webpage out of date? 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.
> This page <> says that an X11
> server is required to make AWT/batik happy, but another page
> <> 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. I think these should be on the FAQ page, since Xvfb seems much more
> awkward than having a true headless AWT.
> 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:
>       -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.
> Thanks,
> Scott Lamb
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message