Yea. I think that adding @Selectable to an Entity would be too tightly coupling data and view. @Selectable is just not quite a record construct. On the other hand, I would be in favor of richer entity annotations that could be used down the road within the frameworks. Things like @Enabled, @Description, @ID (already there), etc. While it's inappropriate to apply specific tooling constructs to entities, it wouldn't be a bad idea to allow entities to expose commonly useful information to the tools/frameworks. I'm sure there will be plenty of debate on what is commonly useful and how to represent it.
I suppose I'd support both. It's not always possible to modify your objects (third-party objects). So I'd start supporting the @Selectable annotation at the controller level. Maybe I'd then add support for some additional entity tags so that I could have the same @Selectable functionality without requiring the objects in my List to have a uniform interface. Thoughts? -Jim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927188#3927188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927188 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
