I need two terms here and I don't know what they are, so I'll make something up and then someone can correct me.
Owning Container: The component that owns the template that your component is referenced from. (eg Your Page) Render Container: The component that wraps your component in the Owning Container's template. Your compont is rendered using t:body. (eg Loop, If, Border/Layout) Events appear to bubble up through the Owning Container. That's not how I expected it to work, but walking through the debugger that's what I saw. Josh On Wed, May 14, 2008 at 6:30 AM, Toby Hobson <[EMAIL PROTECTED]> wrote: > I've now managed to trigger an event in my component and handle it in the > enclosing page but is there a way to make the event "bubble" up the > component tree so that if a page doesn't handle the event, Border.java will. > Basicall I'm looking for the event to behave like a RuntimeException - it > will keep moving up until it's handled > > Toby > > ----- Original Message ---- > From: Toby Hobson <[EMAIL PROTECTED]> > To: tapestry <users@tapestry.apache.org> > Sent: Wednesday, 14 May, 2008 2:00:43 PM > Subject: Event bubbling > > Hi Guys, > > I would like to define an area at the top of my border.tml to show messages > which may be "flashed" to the user. Ideally pages and nested components will > be able to set the message that will be displayed here. I was thinking of > allowing pages and components to fire a custom event, which will then bubble > up to border.java where it set the message. Does this seem like a good idea? > and if so how do I fire a custom event from my pages/components? > > Thanks > > Toby > > > > > -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox.
