On Tue, Mar 4, 2014 at 10:03 PM, novamine118 <[email protected]> wrote: > I'm currently running into stackoverflow errors when jenkins tries to render > my script.
f:repeatable creates an invisible prototype block (class="repeated-chunk to-be-removed") which it copies and makes visible when you click the Add button. I suspect the generation of the HTML for the prototype is triggering recursion. Some other form controls, notably f:hetero-list, use l:ajax to load the config of children only on demand, which would presumably break the cycle. I wonder if making f:repeatableProperty wrap its st:include in l:renderOnDemand + l:ajax would do the same for homogeneous lists. If so, you could work around the problem without patching Jenkins by inlining f:repeatableProperty into your config page (it is short) and making that change. Not for the weak of heart. If my guess is right, probably f:repeatableProperty should be fixed in Jenkins core so it works out of the box with recursive data types. BTW the trunk version of the documentation for f:repeatableProperty notes that you usually need to add your own f:repeatableDeleteButton. This was probably not documented before because not many people seem to use this tag yet. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
