n/m, it turns out there was another, non-tapestry-related cause for the problem I am seeing
On Thu, Sep 29, 2011 at 8:27 AM, Ray Nicholus <rnicho...@widen.com> wrote: > I have a component with two levels of embedded components, like so: > > > <component1> > <t:zone> > <t:component2> > </t:zone> > <component1> > > <component2> > <t:component3> > <component2> > > In component 1, I declare a static String with the property annotation. > That property is passed to component 2, and component 2 passes it on to > component 3. So, the property in component 3 is bound to the definition in > component 1. However, when the zone in component 1 is updated, the binding > to component 1 for this property is lost. I can see that the binding to > component 2 exists, but not to component 1 anymore. > > Any idea why this is happening? >
