[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=all ] Dan Allen updated JBSEAM-2299: ------------------------------ Attachment: JBSEAM-2299-v1.txt I can confirm that this happens when you run the following sequence of seam-gen commands: ./seam new-entity ./seam generate-ui The UI generation is blind to the version property and unknowningly creates an input field for it. I have attached a patch which excludes the input field if the property is the version property, which is available on POJOClass <#if property != pojo.versionProperty> <#include "editproperty.xhtml.ftl"> </#if> That, at least, fixes the breakage. Now the question is, should we hide the version property all together? That is another issue entirely. I am thinking we probably should. In that case, this logic is going to have to be applied deeper. But it is easy to do if you like looking a FreeMarker templates all day. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira