Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 22322 invoked from network); 20 Jun 2007 12:26:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jun 2007 12:26:49 -0000 Received: (qmail 81645 invoked by uid 500); 20 Jun 2007 12:26:51 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 81601 invoked by uid 500); 20 Jun 2007 12:26:51 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 81589 invoked by uid 99); 20 Jun 2007 12:26:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jun 2007 05:26:50 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jun 2007 05:26:46 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6F82B7141AA for ; Wed, 20 Jun 2007 05:26:26 -0700 (PDT) Message-ID: <9667471.1182342386453.JavaMail.jira@brutus> Date: Wed, 20 Jun 2007 05:26:26 -0700 (PDT) From: "Mario Ivankovits (JIRA)" To: dev@myfaces.apache.org Subject: [jira] Commented: (MYFACES-1666) HtmlResponseWriterImpl implements different encoding behaviour for the two writeText methods In-Reply-To: <12897303.1182341248042.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MYFACES-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506512 ] Mario Ivankovits commented on MYFACES-1666: ------------------------------------------- Its not that it might confuse me, but it allows one to reuse this configuration for other "non ri compatible" stuff too ... which I think is not good. I'd like it to have it fine grained. Just to make it a little bit more complicated to find a conclusion ;-) I think we can drop the word "STRICT", SUCCESSIVE_SPACE_ENCODING would be sufficient. > HtmlResponseWriterImpl implements different encoding behaviour for the two writeText methods > -------------------------------------------------------------------------------------------- > > Key: MYFACES-1666 > URL: https://issues.apache.org/jira/browse/MYFACES-1666 > Project: MyFaces Core > Issue Type: Bug > Components: General > Affects Versions: 1.1.5 > Reporter: Manfred Geiler > Assignee: Manfred Geiler > > HtmlResponseWriterImpl implements different behaviour for the two writeText methods: > * writeText(Object value, String componentPropertyName) does not encode successive spaces and newlines > * writeText(char cbuf[], int off, int len) does encode successive spaces and newlines > RI does not encode in both variants. > IMO both methods SHOULD encode successive spaces and newlines to render the corresponding HTML syntax (  and
). > Therefore we should (re)add this feature and make it switchable via a MyFaces Option "STRICT_RI_MODE" or something like that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.