Hi Geoff, thanks for your response.
I'm not really sure. Since I already move the code from the component to
the page . But as I recall the sZone div is there, only it didn't attached
to the Tapestry.ZoneManager. Yes, it could be the problem. We have zone
that contain blocks and then inside the bl
Right before you send the request that fails, if you use your browser's web
inspect the page DOM, can you see the sZone div? If not, then that's the
problem: the failing response would be referring to a zone that the client
doesn't know about. This looks quite likely since your conditional blocks
c
I see nothing wrong with your nested components approach, and there is
nothing wrong with having a component render multiple zones as you are
doing. I don't know the cause of your client-side exception, but I think
your code must be very, very close to correct.
On Thursday, 27 March 2014, abangkis
Hai Geoff thanks a lot for trying :)
I try to explain it better. Basically I have a survey object, that contains
survey info and list of section object. The section object contains section
info and list of question object. What we want to do is give the user the
ability to fill the survey info, se
Sorry, I tried to draw a model of your page but I don't quite get it.
The techniques used in that JumpStart page's components may have a problem when
they're nested deeper. They're done better in the JumpStart preview for T5.4:
http://jumpstart.doublenegative.com.au/jumpstart7/together/
Or maybe someone has an example of a single page site made with tapestry.
I've tried jumpstart
http://jumpstart.doublenegative.com.au/jumpstart/together/ajaxcomponentscrud/personsit's
something similar but able to be nested 3-4 component deep.
Thanks for any clue.
Cheers.
On Tue, Mar 25, 2014 a
