I am running into a problem with entity bean removal where the pk is null,
which causes most everything passed (and including)
Application.synchronizeEntitiesWithinTransaction() to fail (called from
EntityContainer.remove()).
Is there any reason why an EntityContext would have its pk set to null? It
looks like that happens just after it has been removed.
What should happen in there are more than one entities assocated with the
current transaction, one is removed, then the second. It looks like the
first will cause all beans in the tx to store, then the bean will be removed
and it's id will be null'd. The second bean will cause all of the beans to
be stored again, which will fail because the first bean has a null id.
I am not really sure if that is what happens, that is just a guess based on
a look at what is going on. I have not written anything to test this
directly, but I would guess that one tx that creates 2 beans then removes
them will fail.
Does anyone have any idea what is going on?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
