Hello All,
I think that the following two issues are bugs in Hibernate Tools or Seam that need to be added to a bug list, but I need someone with more Seam and Hibernate Tools knowledge to verify this or tell me that I am wrong:
(1) If you use annotated EJB3 entities to generate a Seam CRUD application, then the generated JSPs are not really usable as the order of the fields in the generated JSPs is different from the order of the fields in the annotated EJB3 entities. This means that you have to manually edit the generated JSPs to get the fields into the correct order. This issue seems to exist whether the process used to generate the CRUD application is (a) generate a database schema from the annotated entities and then generate the CRUD application from the generated schema, or (b) generate the CRUD application directly from the annotated entities.
(2) If you use annotated EJB3 entities to generate a Seam CRUD application, then the generated JSPs will include any EJB3 @Version property in the search form, the add form, and the update form. I think that an @Version property should not appear in an add form or an update form, and being editable in the update form may upset the application's optimistic locking.
Many thanks,
Bruce.
