Sure. I solved the problem by explicitly specifying the zone ID. I then passed this zone ID into sub components. Any handlers in the sub components that needed to return the contents of the zone (for zone updates) returned false and delegated to the parent component, which returned the zone contents. I found that simply passing the Zone element to my sub components didn't work as expected. After the first zone update, the clientId was null.
On Fri, Jul 20, 2012 at 10:27 AM, Emmanuel DEMEY <demey.emman...@gmail.com>wrote: > Hi > > Can you share yoru solutions, maybe for other developpers with the same > problem. > > Thx > > Manu > > 2012/7/20 Ray Nicholus <rnicho...@widen.com> > > > As usual, I posted when I should have spent a couple more minutes > thinking > > about the problem. Please disregard. > > > > On Fri, Jul 20, 2012 at 9:28 AM, Ray Nicholus <rnicho...@widen.com> > wrote: > > > > > I have a zone on a parent component. This zone contains a loop. The > > loop > > > references another component, which itself contains a loop. This final > > > loop creates eventlinks which reference the zone on the parent > component. > > > When one of these eventlinks are triggered, the zone on the parent > > > component "refreshes". However, the eventlinks now think the zone is > > null, > > > so an ajax request does not occur when triggering one of the eventlinks > > > again. Any idea how I can fix this? > > > > > > -- > Emmanuel DEMEY > Ingénieur Etude et Développement > ATOS Worldline > +33 (0)6 47 47 42 02 > demey.emman...@gmail.com > http://emmanueldemey.fr/ > > Twitter : @EmmanuelDemey >
