Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <1050807234.1203231035196.JavaMail.jira@brutus>
Date: Sat, 16 Feb 2008 22:50:35 -0800 (PST)
From: "Antonio Gallardo (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Closed: (COCOON-2158) XMLByteStreamCompiler hard-coded
 limits of 0xffff Strings prevents large XML documents from being handled in
 Cocoon
In-Reply-To: <3113726.1199396794044.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COCOON-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Gallardo closed COCOON-2158.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2-dev (Current SVN)
                   2.1.12-dev (Current SVN)

> XMLByteStreamCompiler hard-coded limits of 0xffff Strings prevents large XML documents from being handled in Cocoon
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: COCOON-2158
>                 URL: https://issues.apache.org/jira/browse/COCOON-2158
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.10, 2.1.11, 2.1.12-dev (Current SVN)
>            Reporter: Eric Meyer
>            Assignee: Antonio Gallardo
>            Priority: Critical
>             Fix For: 2.1.12-dev (Current SVN), 2.2-dev (Current SVN)
>
>         Attachments: cocoon-xmlbytestream-bigstrings.patch, cocoon-xmlbytestream.patch
>
>
> The hard-coded limits in XMLByteStreamCompiler prevent Cocoon from handling large XML documents.
> See the methods writeString and writeAttributes for the hard coded arbitrary maximums:
> if (i > 0xFFFF) throw new SAXException("Index too large");
> if (attributes > 0xFFFF) throw new SAXException("Too many attributes");
> Additionally, the hand-coded bit manipulation is pretty difficult to change in order to work around this.
> I am attaching a patch for 2.1.11 that updates the existing JUnit test case to reproduce the problem, as well as a fix to the problem that uses the DataInputStream and DataOutputStream for the low-level bit manipulation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.