persistence@glassfish.java.net

[Fwd: bugs or user error?]

From: Marina Vatkina <Marina.Vatkina_at_Sun.COM>
Date: Mon, 28 Nov 2005 17:43:34 -0800

Team,

This is another email that I've sent on Tuesday
with no luck of getting through :(.

thanks,
-marina

-------- Original Message --------
Subject: bugs or user error?
Date: Tue, 22 Nov 2005 13:20:24 -0800
From: Marina Vatkina <marina.vatkina_at_sun.COM>
To: "persistence_at_glassfish.dev.java.net" <persistence_at_glassfish.dev.java.net>

Team,

I encountered the following problems while running my simple test:

1. With property-based persistence (the default, right?), if I do *not*
have a field that matches exactly the name of property for lazy loading
(e.g. 'cust' vs. getCustomer()), I get the following warning in Java SE
(I didn't check Java EE yet):

--Weaving for valueholders not enabled for class [entity.Order] because it does
not have field [customer].

2. Remove of an instance fetched in the same tx throws an exception that
it's detached:

Exception in thread "main" java.lang.IllegalArgumentException: Entity must be
managed to call remove: entity.Customer_at_10849bc, try merging the detatched and
try the remove again.
        at
oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:2711)

        at
oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerImpl.remove(EntityManagerImpl.java:117)

Are these bugs or my errors?

thanks,
-marina