Hmm... I've stripped my example down to it's bare bones and events are now bubbling up... I must be doing something stupid in my original code. And yes, the parent component is in the components package, it's in mybasepackage.components.
On 2 July 2013 16:19, Howard Lewis Ship <hls...@gmail.com> wrote: > This is odd; it feels like something in Tapestry that's too rock-solid to > fail. Is there any chance the parent class is not being instrumented as a > component class? What package is it in? > > > On Tue, Jul 2, 2013 at 1:58 AM, Lance Java <lance.j...@googlemail.com > >wrote: > > > As I said in my previous message, I've tried triggerEvent on the > > ComponentResources and ComponentResources.getContainerResources(). > Neither > > bubble up to the parent. > > > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com >
