Hibernate and JDK 8

jmnarloch · **Joined:** Wed Aug 06, 2014 4:42 pm **Posts:** 1

Today I had this stunning idea, how cool would it be to access my Hibernate Query result with a Java 8 stream manner.
I begun to wonder, not able to find any regarding article or discussion -
Do you have any plans for moving the Hibernate interface to Java 8?

For instance adding support for java.lang.Optional or accessing the query results through Stream API. As a sneak peak I could figure out at least a couple of exaples of such API:

Code:

Optional<Event> optional = session.getOptional(Event.class, id);

// or through Query interface
Optional<Event> optional = session.createQuery("from Event where id = :id").setParameter("id", id).optionalResult();

Code:

List<Event> events = session.createQuery("from Event")
                                       .stream()
                                       .filter(e -> e.getTitle == "Java 8") // does some optional filtering or any other operation on the result set
                                       .collect(Collectors.toList())

Additionally I could think of using streams and lambdas to be used for building the query in manner similar like the LINQ does, although this would be probably be an idea for an entirely new project ;)

So I was mostly interested what is your opinion and plans on this matter?

sanne.grinovero · **Posted:** Fri Aug 15, 2014 7:11 am

Hi,
I love your idea, and I guess there is much more we could do.

I've notified the developer's mailing list, would be great if you could join us there: http://lists.jboss.org/pipermail/hibernate-dev/2014-August/011657.html
Registration details, and IRC channels are described here: http://hibernate.org/community/

The main problem we are facing is that we have an extremely large user base which isn't moving to Java8 yet, so the "classical API" needs to be available for longer and be compiled with JDK7 compatibility.

We can of course create a new module, I expect this would initially include some kind of syntax translation - also to allow for quick turnarounds and fast improvements - wrapping the classical module. In a second phase we could improve the integration to bypass the classical API and expose internals more efficiently, possibly by then we might be ready to merge the module and baseline on Java8.