Ok, thanks both for your help...

I 'll see if I can modify Tree's eventlink behaviour to have the needed
information.

I 'll update here if I reach some progress

cheers and thanks

Nicolás.-


On Wed, May 23, 2012 at 12:59 PM, Arno Haase <
[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sorry, my mistake - I replied without really thinking...
>
> I was thinking about a similar phenomenon when a loop contains links
> that refer to the loop variable, e.g. as their context. Then you need
> to use 'deferred="true"' with the links.
>
> As Lance wrote, there may not be analogous support for trees in a loop.
>
>
>
>
> Am 23.05.2012 16:44, schrieb Nicolas Barrera:
> > Arno, sorry can you send me the link of the javadoc you 're looking
> > at? 'cause I couldn't find nothing about deffered in
> >
> http://tapestry.apache.org/5.3.3/apidocs/org/apache/tapestry5/corelib/components/Loop.html
> >
> >  Lance, I 'm thinking about what you said and the loop and form
> > relationship,
> >
> > I don't know if this is the real problem but what I could see is
> > that as I got t:model="getTreeModel(loopValue)" the first time
> > (when the tree is first rendered) all values are ok and the tree
> > renders.
> >
> > after that when i try to expand a branch a method on the Tree
> > component (I think that it is the onExpandChildren method)  is
> > called that method tries to retrieve the model of the tree
> > component by calling this.model and it's like it tries to execute
> > getTreeModel(loopValue),
> >
> > can't this value be cached in the component? is it that conduits
> > are never cached?
> >
> > sorry but I think I 'm not understanding the basic of conduits.
> >
> > cheers
> >
> > Nicolás.-
> >
> >
> > On Wed, May 23, 2012 at 10:55 AM, Lance Java
> > <[email protected]>wrote:
> >
> >> I'm not 100% sure but I think you might have encountered a tricky
> >> issue. The Loop component uses the "encoder" property to
> >> integrate with the Form component so that the list is serialized
> >> to a hidden form element and then deserialized when the form is
> >> posted. I don't think that the same kind of integration exists
> >> between Loop and Tree.
> >>
> >> Perhaps someone has a workaround for you but I can't think of one
> >> off the top of my head.
> >>
> >> -- View this message in context:
> >>
> http://tapestry.1045711.n5.nabble.com/T5-3-s-Tree-in-a-Loop-tp5713347p5713351.html
> >>
> >>
> Sent from the Tapestry - User mailing list archive at Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >>
> >>
> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk+9CVkACgkQbmZsMyUPuXT1SgCgs8xMORc68C5ZxhEPTSlqID7M
> hOsAnAtse28SA7Lsg/JgIMrLtLRKgreg
> =4lmt
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to