I have a beaneditor inside an Ajax loop that is inside a form. One of
the attributes needs to be a palette. When I try to simply add it as
a parameter, it doesn't show up. It looks like it would work if I
skip using the beaneditor and just add all the fields manually. Is
there a reason this doesn't seem to work or am I overlooking something
silly?
Also is there a way for me to tell Tapestry to use the Palette
automatically whenever it tries to render this particular attribute
inside of a beaneditor or beaneditorform?
Thanks for any suggestions.
Mark
<div t:type="ajaxformloop" t:id="ticketClasses"
source="event.ticketClasses" encoder="ticketClassEncoder"
value="ticketClass">
<t:beaneditor object="ticketClass">
<!-- This is the part that doesn't show up when it is within the beaneditor -->
<p:discountDefinitions>
<t:palette t:id="discountDefinitions"
selected="ticketClass.discountDefinitions"
encoder="discountDefinitionEncoder" model="discountDefinitionsModel"/>
</p:discountDefinitions>
</t:beaneditor>
<t:removerowlink>remove ticket class</t:removerowlink>
<p:addRow>
<t:addRowLink
t:zone="ticketClasses">Add a ticket class</t:addRowLink>
</p:addRow>
</div>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
