Perhaps this is a totally bad idea, but I'd like to make Tiles out of
portions of forms that get reused a lot (ala address).
How I've done this is to pass a bean from my form into the tile when
inserting it.  However, the rendered HTML doesn't contain the name of the
bean I passed in to the tile, and so none of the setters will work.  Here is
some relevant code:

Calling the tile from a page:

        First Example: comes from the firstTileList property of the
TileExampleForm<BR>
        <tiles:insert name="tile.example" flush="false">
                <tiles:put name="actionTileBean" beanName="TileExampleForm"
beanProperty="firstTileList" beanScope="request" />
        </tiles:insert>

Inside the actual tile (note non-relevant code has been ommitted)

        <tiles:importAttribute name="actionTileBean" ignore="false"/>
        <nested:root name="actionTileBean">
                .
                .
                .
        <nested:iterate id="action" property="actionList">
          <tr>
          <td>
  
          <nested:equal name="actionTileBean" property="selectable"
value="true">
          <nested:checkbox property="selected"/>
          </nested:equal>
  
          <nested:write property="actionId" />
          </td>

Where firstTileList (that becomes actionTileBean) is a normal bean with a
collection called actionList, holding beans that have a boolean selected
property.

Is this just a bad idea or is there a good, clean way to do this?

Chip Paul
Sr Software Engineer
ComFrame Software Corporation
�
Listen.Understand.Innovate
www.comframe.com
 

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

Reply via email to