You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Morten Damsgaard-Madsen <mo...@hotmail.com> on 2004/04/12 12:46:54 UTC
Stuck with upgrade
Hi all
I'm only a user so don't get too technical ;-)
I upgraded my forrest installation to the newest CVS today.
However, when I try to build my old website from version 5.1 I get the
following error:
------------------------------------------------------------------------
cocoon 2.1.4
Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
X [0] index.html BROKEN:
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException: java.lang.RuntimeException:
org.xml.sax.SAXException: Attempt to output character of integral value
229 that is not represented in specified output encoding of .
Total time: 0 minutes 3 seconds, Site size: 0 Site pages: 0
BUILD FAILED
E:\forrest\targets\site.xml:66: Java returned: 1
I can't figure out what it means and a freshly seeded site builds
without a hiccup.
Oh and btw: why are there no margins in the PDF files? And can I set it
to A4 size?
Thx in advance
Morten
Re: Stuck with upgrade
Posted by Juan Jose Pablos <ch...@che-che.com>.
Morten,
Morten Damsgaard-Madsen wrote:
>
> I can’t figure out what it means and a freshly seeded site builds
> without a hiccup…
>
>
Open a jira bug with this information plus a copy of your site.xml file.
>
> Oh and btw: why are there no margins in the PDF files? And can I set it
> to A4 size?
Check the contents on the skinconf.xml file
Re: Stuck with upgrade
Posted by Dave Brondsema <da...@brondsema.net>.
Morten Damsgaard-Madsen wrote:
> Hi all
>
>
>
> I’m only a user so don’t get too technical ;-)
>
>
>
> I upgraded my forrest installation to the newest CVS today.
>
>
If you want to try the latest development code, we are using subversion
instead of CVS now. http://xml.apache.org/forrest/build.html explains
how to check out the code.
I don't think that will fix your bug, though.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: Stuck with upgrade
Posted by Brian Brewer <bb...@tregyr.com>.
Looks like a character encoding problem on your side. If the freshly
seeded site works, then you are apparently crossing your charsets. Look
in each of the xml/xsl declaration lines (as well as the declaration
line in your index page) and make sure they are each using a charset
that supports any special characters you might be using on your index.
If you are trying to use foreign characters, make sure you are using one
of the ISO charsets and that every page uses this charset. Hope this helps!
Brian
Morten Damsgaard-Madsen wrote:
> Hi all
>
> I’m only a user so don’t get too technical ;-)
>
> I upgraded my forrest installation to the newest CVS today.
>
> However, when I try to build my old website from version 5.1 I get the
> following error:
>
> ------------------------------------------------------------------------
>
> cocoon 2.1.4
>
> Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
>
> ------------------------------------------------------------------------
>
> X [0] index.html BROKEN: java.lang.RuntimeException:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.RuntimeException: org.xml.sax.SAXException: Attempt to
> output character of integral value 229 that is not represented in
> specified output encoding of
>
> Total time: 0 minutes 3 seconds, Site size: 0 Site pages: 0
>
> BUILD FAILED
>
> E:\forrest\targets\sitexml:66: Java returned: 1
>
> I can’t figure out what it means and a freshly seeded site builds
> without a hiccup…
>
> Oh and btw: why are there no margins in the PDF files? And can I set
> it to A4 size?
>
> Thx in advance
>
> Morten
>
Re: Stuck with upgrade
Posted by Juan Jose Pablos <ch...@che-che.com>.
Sju,
>
> It looks like a problem I had a while ago, the error message is the
> same. It turned out that the Xalan version used in Cocoon 2.1.4 (Xalan
> 2.5.2) introduced a bug regarding handling of non-ascii characters (be
> it 8859-x or utf-8 or anything in the upper half of the 8-bit range).
> The problem vanished if I replaced version 2.5.2 with the recent 2.6.0
> (this bug did not exist in earlier versions of Xalan, and is thus not a
> problem in Forrest 0.5.1, which uses Xalan 2.5.0 IIRC).
Replacing the xalan library fix this issue. Upgrade to cocoon 2.1.5 will
resolve this issue.
Re: Stuck with upgrade
Posted by Sjur Nørstebø Moshagen <sj...@kolumbus.fi>.
På 12. apr. 2004 kl. 13.46 skrev Morten Damsgaard-Madsen:
> However, when I try to build my old website from version 5.1 I get the
> following error:
...
> -----------------------------------------------------------------------
> -
>
> cocoon 2.1.4
>
> Copyright (c) 1999-2004 Apache Software Foundation. All rights
> reserved.
>
> -----------------------------------------------------------------------
> -
>
> X [0] index.html BROKEN:
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.RuntimeException: java.lang.RuntimeException:
> org.xml.sax.SAXException: Attempt to output character of integral
> value 229 that is not represented in specified output encoding of
It looks like a problem I had a while ago, the error message is the
same. It turned out that the Xalan version used in Cocoon 2.1.4 (Xalan
2.5.2) introduced a bug regarding handling of non-ascii characters (be
it 8859-x or utf-8 or anything in the upper half of the 8-bit range).
The problem vanished if I replaced version 2.5.2 with the recent 2.6.0
(this bug did not exist in earlier versions of Xalan, and is thus not a
problem in Forrest 0.5.1, which uses Xalan 2.5.0 IIRC). The new version
is available at:
http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/lib/endorsed/
Since this problem is actually a Cocoon-problem, and not specific to
Forrest, I never thought of filing a bug report. But it might be a good
thing to file one, both to inform other people of the existence of the
bug, and as a reminder for testing against new versions of Cocoon. I'll
try to get around filing one (haven't done that before;).
Sjur