I am just researching JPA and session beans. I have labored via a simple database model (schema designed using MySQL Work bench) and used an IDE (NetBeans) wizard to create the JPA entity classes and session beans.

My question has related to a suitable workflow once the data model changes. For instance, basically give a column to some table, perform some IDE's have features which will update entity classes and session beans to mirror the brand new underlying data structure? Or are these changes best handled by hand?

I just read this answer on SO, however the answer was a little beyond my experience to date.

I have labored via a simple database model (schema designed using MySQL Work bench) and used an IDE (NetBeans) wizard to create the JPA entity classes and session beans.

To my experience, these produced organizations are frequently not perfect (e.g. you receive characteristics for FK rather than relations). I thus consider them like a beginning point, and surely not really a end result.

(...) For instance, basically give a column to some table, perform some IDE's have features which will update entity classes and session beans to mirror the brand new underlying data structure? Or are these changes best handled by hand?

I am unaware of any tool supporting perfectly round-trip engineering, particularly when utilizing a bottom-up approach i.e. when beginning in the database schema (some companies let it update a schema when utilizing a high-lower approach i.e. when beginning in the organizations and mappings but this is not perfect either) and changes are IMO best handled by hand.

Really, Personally, i consider JPA code generation pedaling (whether you utilize a high-lower or perhaps a bottom-up approach) mostly as "bootstrapping" tools, they assist to obtain things began. But sooner or later, you will need to start syncing things manually (that is where migration tools such as the one pointed out within the question you associated with are helpful).