Looks like the ServiceRegistry pattern is getting quite popular in
Hibernate Search.
There are three default implementations (of three services) which are
provided by the hibernate-search-engine itself.
Essentially the hibernate-search-engine code looks it up, and loads
from its very same jar; I'm
Hello all,
Hibernate Search 5.1.1.Final is now released and available in Maven Central.
http://in.relation.to/Bloggers/ACommunityImprovedVersionOfHibernateSearch511Final
Best Regards,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
ht
The difficulty is recognizing this as an exception condition, which I'd
really prefer to do. But I just don't see a way to accomplish that without
tables keeping a "nature" indicating how they are used.
On Thu, Mar 19, 2015 at 3:35 AM, Emmanuel Bernard
wrote:
> Oops, Adding the mailing list.
>
Oops, Adding the mailing list.
Thanks for the input, we went for two explicit table names in the OGM test.
Looks like we are aligned.
Emmanuel
> On 18 mars 2015, at 18:59, Steve Ebersole wrote:
>
> Well considering I am the only recipient... ;)
>
> I have actually seen this scenario in one
