BLOCK RENDERBLOCK usage does not support multiple references across dom space
-----------------------------------------------------------------------------

                 Key: TAPESTRY-2072
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2072
             Project: Tapestry
          Issue Type: Bug
          Components: Core Components
    Affects Versions: 4.1.3
         Environment: XP Pro, eclipse-3.3.1, jre-1.5.0_06, apache-maven-2.0.8
            Reporter: Kenneth William


BLOCK RENDERBLOCK usage does not support multiple references across dom space.

The following code produces invalid dom ID's due in part that the dom space 
requires unique ID's... regardless, there is no way to operate BLOCK 
RENDERBLOCK using multiple references to the same BLOCK.

<span jwcid="[EMAIL PROTECTED]">

<table width="100%" border=1>

     <tr>

          <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>

     </tr>

</table>

</span>

 

-- definition

<div jwcid="[EMAIL PROTECTED]">

     <div jwcid="@RenderBlock" 

          block="ognl:components.autoPagingContent" />

</div>

<div jwcid="[EMAIL PROTECTED]">

     <div jwcid="@RenderBlock" 

          block="ognl:components.collectionContent" />

</div>

<div jwcid="[EMAIL PROTECTED]">

     <div jwcid="@RenderBlock" 

          block="ognl:components.autoPagingContent" />

</div>


The above produces hidden form id's
     value="tableSizeSelect_0,pagingSpanSelect_0,...

as opposed to
      value="tableSizeSelect,pagingSpanSelect,...

Subsequent usage of parameters to components and page properties all become 
hosed and the app fails to operate.

Maybe a new component should be invented to decorate this usage in order to 
articulate multiple references across the do space. The infrastructure is 
certainly there to make this feasible... SCRIPT.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to