Kodo.persistence.ArgumentException: You cannot perform operation persist on...

Question

Hello,
I'm doing the following:
User user = new User("Dave", "[email protected]");
dao.begin(); // calls entityManager.getTransaction().begin();
dao.create(user); // calls entityManager.persist(object);
dao.commit(); // calls entityManager.getTransaction().commit();
And I get the following stack trace:
Feb 19, 2006 11:26:12 PM org.springframework.web.servlet.FrameworkServlet
processRequest
SEVERE: Could not complete request
<4|false|4.0.0EA3> kodo.persistence.ArgumentException: You cannot perform
operation persist on detached object "sofa.model.User@36e7a9". This
operation only applies to managed objects.
FailedObject: sofa.model.User@36e7a9
     at kodo.kernel.BrokerImpl.getDetachedException(BrokerImpl.java:2481)
     at kodo.kernel.BrokerImpl.persist(BrokerImpl.java:2426)
     at kodo.kernel.BrokerImpl.persistSafe(BrokerImpl.java:2379)
     at kodo.kernel.BrokerImpl.persist(BrokerImpl.java:2366)
     at kodo.kernel.DelegatingBroker.persist(DelegatingBroker.java:1275)
     at kodo.persistence.EntityManagerImpl.persist(EntityManagerImpl.java:
519)
     at sofa.jpa.JpaDao.create(JpaDao.java:23)
     at sofa.controller.SignUpController.processFormSubmission
(SignUpController.java:42)
... and so on
My User class:
@Entity(access=AccessType.FIELD)
public class User {
     @Id(generate=GeneratorType.AUTO)
     private Long id;
     private String name;
     private String emailAddress;
     private String password;
     public User(String name, String emailAddress) {
          this.id = System.currentTimeMillis(); // workaround for bug
          this.name = name;
          this.emailAddress = emailAddress;
... getters and setters
Any ideas?
thanks,
dave

Answer 1

The problem is that "id" is auto-generated, but you're initializing it
to a non-default value. This makes Kodo think that this is an existing
database object.
I suggest downloading EA 4 from www.solarmetric.com. It solves previous
issues with null primary key values, so you should be able to leave "id"
null and therefore avoid confusing Kodo by initializing "id" yourself.
(Note, however, that EA 4 implements the public draft of the spec, and
there have been changes to some annotations.)