My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 79: Anonymous tag columns not displaying correctly.
1 person starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  extremec...@gmail.com


 
Reported by extremec...@gmail.com, Jan 30, 2008

 In my table, I'm trying to make two anonymous columns that will
 contain "edit" and "delete" buttons. The code looks like this :
 <jmesa:htmlColumn title="" sortable="false" filterable="false">
     // Inner content to create the HTML EDIT button
 </jmesa:htmlColumn>
 
 <jmesa:htmlColumn title="" sortable="false" filterable="false">
    // Inner content to create the HTML DELETE buttoon
 </jmesa:htmlColumn>
 
 It seems that when I try to make more than one column that doesn't
 specify a property, it doesn't quite work as expected. The delete
 column is repeated twice. I get two columns with 'delete'  buttons and
 no 'edit'. Is this a bug in jMesa?
 
Jan 30, 2008
#1 extremec...@gmail.com
It is a bug, but only for the tags.... Behind the scenes the values for the table are
put into a Map for the displayable rows to deal with the JSP parsing that happens in
the column body. So in essence your items transform into a Map for display purposes.
There are no limitations of this as sorting and filtering happens with the real
items. Also, if you use the ItemUtils from your custom cell editors it works
transparently with this notion. However, you did find a limitation of sorts. I am
going to list this as an issue and do some checking.

You can easily do what you want though by just declaring a column property as a
placeholder...meaning not a real item property. This is a supported notion, although
I also want to be able to support anonymous columns.

<jmesa:htmlColumn property="edit" title="&nbsp;">edit</jmesa:htmlColumn>
<jmesa:htmlColumn property="delete" title="&nbsp;">delete</jmesa:htmlColumn>

Aug 14, 2008
#2 ghillert
Just stepped over this issues as well. I think the current work-around is not intuitive. 

Powered by Google Project Hosting