Return-Path: X-Original-To: apmail-incubator-deltaspike-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-deltaspike-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 01DB2F2E3 for ; Mon, 22 Apr 2013 05:45:41 +0000 (UTC) Received: (qmail 83690 invoked by uid 500); 22 Apr 2013 05:45:40 -0000 Delivered-To: apmail-incubator-deltaspike-dev-archive@incubator.apache.org Received: (qmail 83562 invoked by uid 500); 22 Apr 2013 05:45:40 -0000 Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: deltaspike-dev@incubator.apache.org Delivered-To: mailing list deltaspike-dev@incubator.apache.org Received: (qmail 83537 invoked by uid 99); 22 Apr 2013 05:45:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 05:45:39 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chkalt@gmail.com designates 209.85.192.178 as permitted sender) Received: from [209.85.192.178] (HELO mail-pd0-f178.google.com) (209.85.192.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Apr 2013 05:45:34 +0000 Received: by mail-pd0-f178.google.com with SMTP id w11so3272654pde.23 for ; Sun, 21 Apr 2013 22:45:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=61eCPluFZewyUm3fMn7yqqgKJK7ImdP/Jn2eNyyd0S0=; b=0JSTxGjhIYvvfMHK7OD4h4IWdbJyPsY70o4tGx80iBKdR9k8SnSPhbun2NHnMf3ijy SbsHT4uKZsUFliLlTatJpJs2+MUTbBlD8t61rgFRvWWXSvOPvOP4nIFYNr+AtgnGhcHg YKZsBCRyL84xh3hlVYFjQ8gIiUChkF+R0C3pbc83yHMJ3yX9JCtVqxt1kbmk5UXWAvtS /xDdgd3YF3beiiLdMRXujTfTZXnfa6v55G5F2fr3znRpyg89B36kci3GgP5/h+HK6qoi MjD0m1masDkCvEfDmHewYvWqnNpAIs/Y9ZFSJ94HiGkAMKparcUSqDCX2SmZKhet8/OL 10ZQ== MIME-Version: 1.0 X-Received: by 10.66.164.6 with SMTP id ym6mr10986094pab.92.1366609512896; Sun, 21 Apr 2013 22:45:12 -0700 (PDT) Sender: chkalt@gmail.com Received: by 10.66.233.161 with HTTP; Sun, 21 Apr 2013 22:45:12 -0700 (PDT) In-Reply-To: <1366574544.17445.YahooMailNeo@web28903.mail.ir2.yahoo.com> References: <1366560521.23403.YahooMailNeo@web28904.mail.ir2.yahoo.com> <1366574544.17445.YahooMailNeo@web28903.mail.ir2.yahoo.com> Date: Mon, 22 Apr 2013 07:45:12 +0200 X-Google-Sender-Auth: DacAuGuQl40s99UwxOhRyfZSKjY Message-ID: Subject: Re: windowId postback detection From: Christian Kaltepoth To: deltaspike-dev@incubator.apache.org, Mark Struberg Content-Type: multipart/alternative; boundary=047d7bacb3ac90200b04daec9219 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bacb3ac90200b04daec9219 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I like the idea of a custom component because it makes it more explicit what the component is used for and perhaps would even provide more control over what is happening. So +1 for a custom component 2013/4/21 Mark Struberg > Gerhard brought up another alternative: simply provide a component which > doesn't render any html but adds the windowhandler.js and stores the > component in the ViewRoot. > > LieGrue, > strub > > > > > ----- Original Message ----- > > From: Romain Manni-Bucau > > To: Mark Struberg ; > deltaspike-dev@incubator.apache.org > > Cc: > > Sent: Sunday, 21 April 2013, 20:56 > > Subject: Re: windowId postback detection > > > > 1 sounds easier to track too > > Le 21 avr. 2013 18:09, "Mark Struberg" a > > =E9crit : > > > >> Hi! > >> > >> There are technically 2 options for extracting the windowId on POSTs: > >> > >> 1.) setting a hidden UIOutput component in the ViewRoot > >> > >> > >> 2.) provide a custom renderkit/ResponseStateManager > >> > >> I think 1.) is much easier. Any input? > >> > >> LIeGrue, > >> strub > >> > >> > > > --=20 Christian Kaltepoth Blog: http://blog.kaltepoth.de/ Twitter: http://twitter.com/chkal GitHub: https://github.com/chkal --047d7bacb3ac90200b04daec9219--