They will, and the spec group has had mentions of that happening and no
response from the EG chair. We should offer a project on our Jira! ;)
On Fri, Dec 2, 2016 at 11:06 AM Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
wrote:
That's a great idea. The only problem with the JPA EG is that
there wasn't
any response to emails in months. We could at least create a JIRA issue for
this. My only concern is that the JPA Jira and other resources are hosted
on
java.net which will be deactivated on April next year.
Vlad
On Fri, Dec 2, 2016 at 6:49 PM, Steve Ebersole <steve(a)hibernate.org>
wrote:
But on Java 6 there is the hack we used to use. Using Closeable instead
and Java 8 recognizing that as well.
On Fri, Dec 2, 2016 at 10:48 AM Steve Ebersole <steve(a)hibernate.org>
wrote:
> +1
>
> we should start collecting a list. And voila:
>
https://github.com/hibernate/hibernate-orm/wiki/Post-JPA-2.1-proposals-wo...
> :)
>
> On Fri, Dec 2, 2016 at 10:31 AM Sanne Grinovero <sanne(a)hibernate.org>
> wrote:
>
> We updated several Hibernate APIs to allow using the
> try-with-resources pattern a while back,
> and I've been finding that quite handy.
>
> Had to write some code using JPA's EntityManager these days; in
> contrast it feels it's stuck somewhere between the stone age and the
> dark ages to not be able to do the same.
>
> Should we propose the same API fixes to the JPA expert group?
>
> Thanks,
> Sanne
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev