Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 95554 invoked from network); 11 Nov 2003 21:54:18 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Nov 2003 21:54:18 -0000 Received: (qmail 79656 invoked by uid 500); 11 Nov 2003 21:54:03 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 79604 invoked by uid 500); 11 Nov 2003 21:54:02 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 79591 invoked from network); 11 Nov 2003 21:54:02 -0000 Received: from unknown (HELO dd2020.kasserver.com) (81.209.148.130) by daedalus.apache.org with SMTP; 11 Nov 2003 21:54:02 -0000 Received: from vafer.org (unknown [134.76.25.103]) by dd2020.kasserver.com (Postfix) with ESMTP id BE76F23881 for ; Tue, 11 Nov 2003 22:53:57 +0100 (CET) Message-ID: <3FB15AE1.2000001@vafer.org> Date: Tue, 11 Nov 2003 22:55:45 +0100 From: Torsten Curdt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: DO NOT REPLY [Bug 23299] - [PATCH] UTFDataFormatException: String cannot be longer than 32k. References: <20031107152727.21622.qmail@nagoya.betaversion.org> <3FAD1258.3070006@virbus.de> <3FAD2640.8070707@vafer.org> <3FB1369E.2030008@virbus.de> <3FB14E15.9070106@vafer.org> <3FB1530E.4040100@virbus.de> In-Reply-To: <3FB1530E.4040100@virbus.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > We don't break anyone's code with the current patch, at least I guess no > one is relying on the exception thrown until now :-) But if you have > already something working, that's better than the current one let's fix > the current behaviour after the release. Or does this temporary solution > do any harm? Well, alright: let's keep it and I'll test and commit it after the code freeze cheers -- Torsten