Hello, I am looking for a Hibernate expert to help me solve this problem. I know I am doing something wrong, but can't figure it out so far. I created a manager object, which is a subclass of an employee object. To implement this subclass relationship I used a discriminator column in the employee table. I also have an EmployeeName object which has a primary key association with Employee. This is a legacy app, and I have no idea why the employee name is in a seperate table. Since it is a legacy app, the values of the primary keys in the employee and the employee name table must stay the same. I need to make an Employee a Manager. To do this, I created a constructor in the Manager class that accepts an Employee. In the constructor, I set all the attributes of the manager with values from the employee class including the id since it needs to stay the same. I then delete the employee object. The manager object now contains the employeeName object. To tell hibernate that the employeeName object needs to be persisted, I set its id attribute to -1. Thats where I get the error listed below. [url removed, login to view]: identifier of an instance of [url removed, login to view] altered from 3030 to -1 I also have attributes of employee that are collections. When I apply them to the mgr object do I have to iterate the entire collection to tell hibernate to save each object? I am looking for someone to help me navigate my way through this problem using hibernate's recommended approach. (no jdbc calls) Hope this makes sense. I am attaching my mapping docs, classes, stack trace, and servlet code.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).