[hibernate-dev] Various expectation changes in hibernate-core after consolidating hibernate-entitymanager
Hardy Ferentschik
hardy at hibernate.org
Wed Apr 27 08:36:58 EDT 2016
Hi,
On Mon, 25-Apr-2016 11:13, Gunnar Morling wrote:
> The strategy approach sounds nice on first thought, but it also adds
> complexity.
+1
> I think the underlying question is: What's the long-term strategy around
> the "Classic API"? Should it remain in place for all times as a complete
> alternative to the JPA API?
>
> Or should we begin to deprecate it and narrow it down in favour of the
> corresponding functionality standardized in JPA, and only functionality not
> present in JPA would be exposed through some kind of unwrap()?
>
> Without having thought about all the implications too much, I'd lean
> towards the latter, in which case I vote for "1. Just move to JPA expected
> exceptions" as part of such larger effort.
+1 My thinking as well.
--Hardy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 496 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hibernate-dev/attachments/20160427/f11dd194/attachment.bin
More information about the hibernate-dev
mailing list