Sorry for my very late reply. It's been a bit chaotic of late.
> - All other tags in tiles-defs.xml require the developer to specify
> explicitely that she wants the expression evaluated: <add-attribute
> expression="${customer.id}"/> instead of <add-attribute value="Customer
> ID"/>. Doing differently for <item> would make this XML even more
> confusing that it already is.
Brett, why were you using <item> instead of <put-attribute> inside the
<put-list-attribute> ?
Is it only because you want two values? (ie value and link)
Could there be other ways to solve this with tags that are supported in
tiles-3
For example something like…
<put-list-attribute name="breadcrumbs">
<add-list-attribute name="customer.id">
<add-attribute expression="${customer.id}" />
<add-attribute
expression="/customers/${customer.id}/salesOrders" />
</add-list-attribute>
<add-list-attribute name="order.id">
<add-attribute expression="${order.id}" />
<add-attribute
expression="/customers/${customer.id}/salesOrders" />
</add-list-attribute>
</put-list-attribute>
> - Do we want to keep maintaining <item> and <bean>, given that today DI
> frameworks provide several better ways to declare those beans?
Not for example if approaches like i wrote above are a satisfactory
solution.
~mck
