Can anyone comment on this finding...
 
Here is PropertySelection template code from Gallery.html
<td width="25%" align="left" NOWRAP>
<span jwcid="@Insert" value="Table Size"/>
<select jwcid="[EMAIL PROTECTED]"
model="ognl:tableSizeModel"
value="ognl:tableSize"
/>
<span jwcid="@Insert" value="Paging Span"/>
<select jwcid="[EMAIL PROTECTED]"
model="ognl:pagingSpanModel"
value="ognl:pagingSpan"
/>
</td>
 
Here is the rendered markup within the form
 
 value="tableSizeSelect,
        pagingSpanSelect,
        foreach,
        If,
        If_0,
        editLinkElse,
        If_1,
        If_0_0,
        editLinkElse_0,
        If_2,If_0_1,
        editLinkElse_1,
        If_3,
        If_0_2,
        editLinkElse_2,
        tableSizeSelect_0,
        pagingSpanSelect_0" />
QUESTION:
 
Why is tapestry naming my hidden id's 
        tableSizeSelect_0
        pagingSpanSelect_0
 
I already specified their names in the BLOCK as
        tableSizeSelect
        pagingSpanSelect
 
Furthermore, Why are they not being used in a replicated fashion across 
definitions. one would assume that if I reused the same block, the same 
ID/INSTANCE would be used ?
 
Hello?
 
Should I jira this? This is all hammering on the usage of Block, RenderBlock 
referencing the same component instance. Everything gets hosed.
 
Can someone confirm a bug here. Please. Thanks
_________________________________________________________________
Helping your favorite cause is as easy as instant messaging. You IM, we give.
http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join

Reply via email to