Mailing-List: contact user-help@pivot.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@pivot.apache.org
Received-SPF: pass (nike.apache.org: domain of gkbrown@mac.com designates
 17.148.16.102 as permitted sender)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Subject: Re: messages that ascend the containment hierarchy
From: Greg Brown <gkbrown@mac.com>
In-reply-to: <20100719145145.D57687@p3c0.erirefr.arg>
Date: Mon, 19 Jul 2010 18:06:57 -0400
Message-id: <A0556573-7FBC-4B6D-B02B-A6C152893F19@mac.com>
References: <20100715230954.T35196@p3c0.erirefr.arg>
 <4C40DE64.1070909@hms.harvard.edu>
 <1773CAE0-D416-412A-9F5A-CB741DD864F9@mac.com>
 <20100719054908.U14433@p3c0.erirefr.arg>
 <9CD5E6D7-E785-4105-A013-36BE4E79F552@mac.com>
 <20100719145145.D57687@p3c0.erirefr.arg>
To: user@pivot.apache.org

> I think of these kinds of events as a part of the public interface of a component.  Listeners respond to events they're interested in.  One such event may be---to use a very verbose and impractical name---"add a new address form".  Or "refresh this data model".  Or "follow this link". Usually these events are dispatched by a push button, but sometimes they can be dispatched from selections in a list or table, or selection made with a radio button or check buttons.

These are exactly the kind of events that EventBus and Pivot's pub/sub API are intended to support. I'd suggest taking a look at one of those - you may find a simpler solution to your problem.