"awhitford" wrote : Good work Kent! I can't wait to try this... | | I can't stress how important this feature is because the reverse engineering approach makes a lot of incorrect assumptions. The Entity bean provides much richer information for CRUD generation. | | Some problems that I have run into with reverse engineering include: | | * I have run into problems dealing with Dates because the database (SQL Server) only has one date type (datetime) for dates, times, and timestamps. However, if you look at my Entity bean, it clearly has the field tagged with a Temporal annotation (@Temporal(TemporalType.DATE)). | | | | * I have run into problems with Enumerated types. To the database, I often store enum values as Strings, so the reverse engineering makes the field a String rather than an enum. My Entity bean has an enum annotated (@Enumerated(EnumType.STRING)). | | | | * I rarely override the columnDefinition (for an enum code or iso code, for example). The reverse engineering translates char(n) columns to be varchar(n), then deployment fails because Hibernate does some validation. | | | | All these things can be customized visually in the existing eclipse GUI for Hibernate Tools. Max is right now working frantically on getting seam-gen integrated into this GUI. So the above problems are really temporary issues. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016078#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...