Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.0 RC2
-
Fix Version/s: 1.0 RC2
-
Component/s: Decorators
-
Labels:None
-
Application server:Tomcat 5.5
Description
When doing something along the lines of:
<display table id="row" name="mylist" decorator="bar.FooDecorator>
<display:column title="name" >
<c:out value="${row.name}"/>
</display:column>
</display:table>
then the implicit 'row'-object used in the JSTL tag is not the FooDecorator instance but the object from the list.
<display table id="row" name="mylist" decorator="bar.FooDecorator>
<display:column title="name" >
<c:out value="${row.name}"/>
</display:column>
</display:table>
then the implicit 'row'-object used in the JSTL tag is not the FooDecorator instance but the object from the list.
If you use the "property" attribute the tag look for the bean property both in the original object and in the decorator, but this can't be done in column body, since displaytag directly esposes the original bean.
So, if you have a bean with a "name" property and a decorator with a "decoratedName" property there is no way to expose an object which will allow both:
bean.getName()
decorator.getDecoratedName()
Anyway, if you use a table decorator there is no reason to also use the column body instead of the (faster) property attribute.