I am perplexed how i am expected to modify a detached entity if my modification can result in some deletions of related entities in pure JPA style.
Before JPA spec, all major persistence frameworks (hibernate, toplink, kodo) recognized such a need and provided a support for this. Not so JPA. I was told by Christian from Hibernate team (thanks), this feature does not fit in JPA entity lifecycle model.
I believe this feature is really crucial, without it i can not modify a detached entity in case modification may result in some related entitty deletion (please correct me if i am wrong).
Idea of rich domain model is negated - businness methods which could delete any entity (fairly obvious case) need reference of EntityManager. It seems to me JPA is not suitable for non-managed environment despite spec calculates with such use.
What programming model is expected for JPA outside of application server?
Is a real chance to use it without non-portable extensions?
[Message sent by forum member 'mstanik' (mstanik)]
http://forums.java.net/jive/thread.jspa?messageID=212489