Return-Path: X-Original-To: apmail-myfaces-dev-archive@www.apache.org Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C5FB10A64 for ; Mon, 4 Nov 2013 13:07:03 +0000 (UTC) Received: (qmail 97110 invoked by uid 500); 4 Nov 2013 13:06:41 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 97086 invoked by uid 500); 4 Nov 2013 13:06:39 -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 96923 invoked by uid 99); 4 Nov 2013 13:06:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Nov 2013 13:06:24 +0000 Date: Mon, 4 Nov 2013 13:06:24 +0000 (UTC) From: "Gerhard Petracek (JIRA)" To: dev@myfaces.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MYFACES-3816) missing window-handling for initial requests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MYFACES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812762#comment-13812762 ] Gerhard Petracek edited comment on MYFACES-3816 at 11/4/13 1:05 PM: -------------------------------------------------------------------- @dora: that wasn't the topic. without an initial redirect or rewriting the url via js, users get unexpected issues even after the second request (if you only use ajax-requests until a browser-refresh). if we would get issues with the tck, we could still do #2. i never said that a redirect is the only choice we have. (it just has less unexpected effects, esp. if you have special logic in your application. furthermore, it doesn't require html5 compliant browsers.) was (Author: gpetracek): @dora: that wasn't the topic. without an initial redirect or rewriting the url via js, users get unexpected issues even after the second request (if you only use ajax-requests until a browser-refresh). if we would get issues with the tck, we could still do #2. i never said that a redirect is the only choice we have. (it just has less unexpected effects, esp. if you have special logic in your application.) > missing window-handling for initial requests > -------------------------------------------- > > Key: MYFACES-3816 > URL: https://issues.apache.org/jira/browse/MYFACES-3816 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-344 > Affects Versions: 2.2.0-beta > Reporter: Gerhard Petracek > Assignee: Leonardo Uribe > > for an initial request there is no window-id added to the url. > (tested with 'url' for javax.faces.CLIENT_WINDOW_MODE) > -> in case of a page refresh a new window-id will be created and it isn't possible to get back the original one. that can also happen with a page-refresh after multiple requests, if only ajax requests are used. > that's a major issue for all scopes based on the window-id. > it can be done with an initial redirect (default in codi) or js (with html5 compliant browsers) -- This message was sent by Atlassian JIRA (v6.1#6144)