This comes up a lot ... probably time to update the FAQ.

Each component in your template must have a unique id 
that is matched against the component specification.

Sounds like you are effectively duplicating a component: 
that is, same component, same configuration, but 
different location.  Please check the specification 
documentation ... there's a copy-of attribute on the 
<component> element that will help you.





--
[EMAIL PROTECTED]

http://tapestry.sf.net
>   Hello,
> 
> I am new to tapestry and maybe wrongly understand its concepts. Isn't it
> possible to reuse components on a page?
> 
> I have to implement a catalog of categories. Each category can have
> subcategories. So, there are current path, current category and
> subcategories.
> 
> My first attempt was as follows:
> HTML:
>     <table>
>       <tr>
>         <span jwcid="eachPathCategory">
>         <td>:\<a jwcid="chooseCategory"><span
> jwcid="insertCategoryName">CategoryName</span></a>\</td>
>         </span>
>       </tr>
>       <tr>
>         <th>Subcategories for: <span
> jwcid="insertCurrentCategory">CurrentCategory</span></th>
>       </tr>
>       <span jwcid="eachSubcategory">
>       <tr>
>         <td><a jwcid="chooseCategory"><span
> jwcid="insertCategoryName">CategoryName</span></a></td>
>       </tr>
>       </span>
>     </table>
> 
>   <component id="eachPathCategory" type="Foreach">
>     <binding name="source" property-path="categoryPath"/>
>     <binding name="value" property-path="category"/>
>   </component>
>   <component id="eachSubcategory" type="Foreach">
>     <binding name="source" property-path="subcategories"/>
>     <binding name="value" property-path="category"/>
>   </component>
>   <component id="insertCategoryName" type="Insert">
>     <binding name="value" property-path="category.name"/>
>   </component>
> 
> But I've got: Template for component CategoryManager contains multiple
> references to embedded component chooseCategory. For insertCategoryName the
> same error. I can work around but it requires specification of additional
> components. Do I really have to define additional components?
> What about reuse of dynamic bindings in different components?
> 
> TIA,
> 
> alex
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> 
> _______________________________________________
> Tapestry-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/tapestry-developer

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to