Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Message-ID: <1704274367.437811266865828218.JavaMail.jira@brutus.apache.org>
Date: Mon, 22 Feb 2010 19:10:28 +0000 (UTC)
From: "Howard M. Lewis Ship (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Subject: [jira] Closed: (TAP5-1024) Submit component should allow return
 values from event handler methods triggered by its event
In-Reply-To: <2095144005.406301266628228152.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAP5-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1024.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> Submit component should allow return values from event handler methods triggered by its event
> ---------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1024
>                 URL: https://issues.apache.org/jira/browse/TAP5-1024
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>
> Currently, the Submit component (and friends, such as LinkSubmit) fire an event that does not support return values.
> It should be capable of returning any "navigational result", just like most events (such as all those fired by the Form itself).
> Ideally, this would be a case of sharing the ComponentEventResultProcessor instance used by the Form itself (as an environmental).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.