Hi,

Several months ago we've taken a decision to use JPA annotations, with Hibernate Session (as opposed to Entity Manager).
We read that it's a valid approach, and we liked the idea (we like Hibernate Session because of HQL and because we already have infrastructure code for it; but we wanted to try out JPA annotations).

Now I see this warning for Cascade Types:
http://stackoverflow.com/questions/4540 ... -cascading
It got me worried... I don't mind about this single oddity (we use Cascade.ALL anyway), but I'm worried it's a general indication that this combination is not often used, and thus doesn't get much testing.
Which might yield additional surprises, next time I get into a corner case, like those "Polymorphic type, that is lazily loaded, and flushed at some unusual point...".

So I'd appreciate input from actual field experience - is this combination (JPA + Session) mature enough for real life production applications?
Or is it one of those things that only look nice on theory?
(Of course no offense for the wonderful Hibernate team that does such great work:) it's totally acceptable to say "we don't test this combination", I'd just like to know).