Turns out that the problem was caused by a misunderstanding in the purpose of
the decorator. In reality, the decorator creates a "field" that doesn't actually
exist - I thought it wrapped a field that *did* exist:
So...my object consists of a list of userId and parentId but the jsp code would be:
<display:table width="75%" name="users" requestURI="gotomodifyuser.do"
decorator="foo.Wrapper" >
<display:column property="userId" title="ID" />
<display:column property="parentId" title="ID" />
<display:column property="link2" title="ID" />
</display:table>
"link2" doesn't actually exist. The wrapper code was changed to:
public String getLink2()
{
return "<a href=\"details.jsp?id="
+ "&action=view\">View</a> | "
+ "<a href=\"details.jsp?id="
+ "&action=edit\">Edit</a> | "
+ "<a href=\"details.jsp?id="
+ "&action=delete\">Delete</a>";
}
and everything now comes back to the page as it should be.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
displaytag-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/displaytag-user
