but that means that you have NO chance to intercept a business-logic call from
a client who is doing an update on an entity that has cascading enabled !!!
Assume 2 entities e.g. person [1:n] address. You have got a business-method
that can be called with person as an attribute only, and the clie
Hi,
according to the specification (Ejb-3_0-spec-persistence.pdf chapter 3.5.2) the
behaviour of @PrePersist and @PreUpdate may be different.
in short words (trying to keep the meaning correct)
@PrePersist and @PreRemove are called before the EntityManger methods persist
and remove are execute
