Making stuff like this optional in 4.x is difficult though because it needs
to tie into the metamodel resolution. Today that process is very
closed-off and static.
On Mon, Jul 28, 2014 at 4:54 AM, Gunnar Morling
wrote:
> 2014-07-28 11:48 GMT+02:00 Sanne Grinovero :
>
> > We'd also love to supp
2014-07-28 11:48 GMT+02:00 Sanne Grinovero :
> We'd also love to support some features (especially the new user types
> such as Date/Time) in Hibernate Search.
>
Ah, right. I've heard requests about the 310 date/time types as well.
>
> I don't think we should require Java8 for all users though,
We'd also love to support some features (especially the new user types
such as Date/Time) in Hibernate Search.
I don't think we should require Java8 for all users though, so I'd
like this to be an independent module.. troublesome with Maven though,
so this wasn't done yet.
--Sanne
On 28 July 201
Hi,
Java 8 introduced a new type Optional which may be used to represent
objects which may be set or not set:
private Optional name;
Hibernate Validator will allow to validate properties of this type in the
next release. Now someone brought up the question whether the same is
planned for ORM
