Return-Path: X-Original-To: apmail-myfaces-users-archive@www.apache.org Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5251C11FB6 for ; Wed, 20 Aug 2014 18:06:27 +0000 (UTC) Received: (qmail 47556 invoked by uid 500); 20 Aug 2014 18:06:24 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 47501 invoked by uid 500); 20 Aug 2014 18:06:24 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 47490 invoked by uid 99); 20 Aug 2014 18:06:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 18:06:24 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wtlucy@us.ibm.com designates 32.97.110.159 as permitted sender) Received: from [32.97.110.159] (HELO e38.co.us.ibm.com) (32.97.110.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 18:06:16 +0000 Received: from /spool/local by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 20 Aug 2014 12:05:55 -0600 Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 20 Aug 2014 12:05:53 -0600 Received: from b03cxnp07029.gho.boulder.ibm.com (b03cxnp07029.gho.boulder.ibm.com [9.17.130.16]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 3EF2719D8026 for ; Wed, 20 Aug 2014 12:05:41 -0600 (MDT) Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id s7KG1w0I3604740 for ; Wed, 20 Aug 2014 18:01:58 +0200 Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id s7KIACDo026518 for ; Wed, 20 Aug 2014 12:10:12 -0600 Received: from d03nm125.boulder.ibm.com (d03nm125.boulder.ibm.com [9.63.34.13]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id s7KIACLI026514 for ; Wed, 20 Aug 2014 12:10:12 -0600 In-Reply-To: References: Subject: Re: Issue with javax.faces.SEPARATOR_CHAR and commandLink X-KeepSent: 82435DBD:C309BAA7-87257D3A:00630AC6; type=4; name=$KeepSent To: "MyFaces Discussion" X-Mailer: IBM Notes Release 9.0.1SHF211 December 19, 2013 Message-ID: From: William Lucy Date: Wed, 20 Aug 2014 14:05:48 -0400 X-MIMETrack: Serialize by Router on D03NM125/03/M/IBM(Release 9.0.1FP1|April 03, 2014) at 08/20/2014 12:05:49 PM MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=08BBF7A9DFF08C568f9e8a93df938690918c08BBF7A9DFF08C56" Content-Disposition: inline X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14082018-1344-0000-0000-0000039A7733 X-Virus-Checked: Checked by ClamAV on apache.org --0__=08BBF7A9DFF08C568f9e8a93df938690918c08BBF7A9DFF08C56 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Hi Leonardo, Thanks for the feedback. I've tested your suggestion, and that seems t= o work fine. JIRA issue opened at: https://issues.apache.org/jira/browse/MYFACES-3919 Regards, Bill Leonardo Uribe wrote on 08/20/2014 01:14:39 PM: > From: Leonardo Uribe > To: MyFaces Discussion > Date: 08/20/2014 01:15 PM > Subject: Re: Issue with javax.faces.SEPARATOR_CHAR and commandLink > > Hi > > 2014-08-20 6:36 GMT-05:00 William Lucy : > > > > > > Hello all, > > > > We've come across an issue while trying to modify the > > javax.faces.SEPARATOR_CHAR - changing it to a non-colon character s= eems to > > break h:commandLink actions. For example, with the separator chara= cter set > > to a hyphen "-", the following navigation does not work (the output= link > > just triggers a refresh): > > > > > > > > > > > > > > > > > > > > This can be observed in MyFaces 2.0.21, 2.1.15, and 2.2.4. A workaround is > > to enable the context parameter > > org.apache.myfaces.RENDER_FORM_SUBMIT_SCRIPT_INLINE, however that parameter > > has been removed in the 2.2 branch. (It's also not a particularly > > desirable workaround.) > > Yes, that's the reason why we remove it. It was legacy stuff from 1.1= /1.2 and > with 2.2 it is the right time to do a cleanup in the codebase. > > > The issue here seems to stem from the oamSubmit.js > > script; in that file there is a call > > > > myfaces.oam.setHiddenInput(formName, formName + ':' + '_idcl', linkId); > > > > which explicitly passes uses a colon separator character. In > > HtmlRendendererUtils.getHiddenCommandLinkFieldname, however, we hav= e > > > > return formInfo.getFormName() + UINamingContainer.getSeparatorC= har > > (FacesContext.getCurrentInstance())+ HIDDEN_COMMANDLINK_FIELD_NAME;= > > > > which will cause the wrong hidden field name to be searched, and th= e broken > > actions seen here. > > > > Is this a bug, or just an accepted limitation of javax.faces.SEPARATOR_CHAR > > use? Thanks for any feedback! > > > > It is a bug. We should not use UINamingContainer.getSeparatorChar(...= ) to > render that hidden field and enforce ':' instead. The reason is the intention > of use javax.faces.SEPARATOR_CHAR is to avoid the collision with css > when you use the ':', but in this case the intention is to create a hidden > field, with no real underlying component, so it is better to let ':'o= n the js > file. Please create an issue in MyFaces issue tracker and I'll fix it= on all > affected branches. > > https://issues.apache.org/jira/browse/MYFACES > > regards, > > Leonardo Uribe > > > Bill Lucy > > IBM RTP WebSphere > > wtlucy@us.ibm.com >= --0__=08BBF7A9DFF08C568f9e8a93df938690918c08BBF7A9DFF08C56--