Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Message-ID: <1882083521.1115082847289.JavaMail.jira@ajax.apache.org>
Date: Tue, 3 May 2005 03:14:07 +0200 (CEST)
From: "Eddie O'Neil (JIRA)" <beehive-dev@incubator.apache.org>
To: beehive-dev@incubator.apache.org
Subject: [jira] Updated: (BEEHIVE-540) Need an equivalent of page inputs for
 nested page flows.
In-Reply-To: <853901060.1114041803431.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/BEEHIVE-540?page=all ]

Eddie O'Neil updated BEEHIVE-540:
---------------------------------

    Fix Version: TBD

Seems likely at this point that we won't get to this before V1 (though it's a great idea!), so I'm going to move this to TBD.  

Comments / disagreements welcome.  :)

> Need an equivalent of page inputs for nested page flows.
> --------------------------------------------------------
>
>          Key: BEEHIVE-540
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-540
>      Project: Beehive
>         Type: New Feature
>   Components: NetUI
>     Versions: TBD
>     Reporter: Thomas Cook
>      Fix For: TBD

>
> I think it would be nice if there was an equivalent of a page input for nested page flows.  Without this, it seems like page/page flow interchangability is slightly lacking.
> Rich and I briefly discussed this, and talked about the possibility of allowing "input" args to the nested flow's begin() method with names that match the action output names of the nesting flow. This however raises the issue of input names and whether they have to be valid Java identifiers. Other ideas are welcome - I'm just filing this to track the issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira