I've tracked and hunted down a small but impacting bug for Hibernate OGM.
I am not sure about the CR status but if you could squeeze this one in, I would be grateful. I have committed it in upstream master and all tests pass.
BTW this bug was also present in the (future) metadata source part of the code (in some form). Inheritance could not have worked before the fix. I'm not sure it works now but that's one step closer :)
as you know I am reviewing the Search documentation and I keep banging my
head against chapter
2 (Architecture) and 3 (Configuration).
This two chapters are most affected by the Search 4 changes and I think we
need to rethink how
we want to describe the system to our users. The current documentation is
a bit of a patch work
were we basically just added things introducing quite a bit of confusion.
For example we in the Architecture we start talking about things like
backend and reader strategy
even before mentioning the IndexManager.
Here is how I think we could arrange the content (correct me from wrong).
The basic idea is that
the IndexManager moves into focus.
I think this is also already implied by the following:
"The default IndexManager implementation is named transactional. This is
the one mostly referred to in this documentation,
unless stated otherwise, and is highly configurable as you can select
different implementations for the reader strategy,
back ends and Directory Providers"
For me the architecture is not as follows:
* each entity can be indexed into one (ore more) Lucene index
* each Lucene index has a IndexManager
* the index manager gives access to directory and reader provider as well
as the backend to be used
* when using properties of the form org.hibernate.search.<index-name>.xyz
you are effectively configuring the
IndexManager for the specified index
* properties of the form org.hibernate.search.xyz are default values which
apply for any index manager if
not overridden explicitly
What do you guys think about this view?
In the configuration chapter I also would like to apply some other
changes. For example, moving "Sharing indexes" into
advanced features. We even mention in the docs that we don't recommend it,
still it appears so early. Besides of that
I would like to rearrange a little the different back-end configurations.
This is in reference to the following;
Re: org.hibernate.HibernateException: /hibernate.cfg.xml not found
30. Sep 2011, 20:02 CET | Link
Gail Badner | gbadner(AT)redhat.com
Regarding Eclipse tools for integrating with Hibernate, I don't use
Eclipse myself, so I've asked on the hibernate-dev mailing list.
The above message was the answer to an inquiry I posted on Sep 28 as
org.hibernate.HibernateException: /hibernate.cfg.xml not found
28. Sep 2011, 17:45 CET | Link
I just updated my eclipse rcp project to use hibernate 3.6.7 and ran the
application an the following exception is thrown:
org.hibernate.HibernateException: /hibernate.cfg.xml not found at
at org.hibernate.cfg.Configuration.configure(Configuration.java:2127) at
The application was running before the update. I have not move the
hibernate.cfg.xml file. It is where it was before the update.
What is wrong?
Thanks for you for taking the time.
University of Nebraska Medical Center
College of Nursing
985330 Nebraska Medical Center
Omaha, NE 68198-5330
Confidentiality Statement: This communication is intended only for the
use of individual or entity to which it is address and may contain
information that is privileged and confidential. If you are not the
intended recipient, or the employee or agent responsible for delivering
communications to the intended recipient, you have receive this
communication in error and are prohibited from reading, printing, or
disclosing any of the information contained in it. If you have received
this communication in error, please notify the sender immediately by
telephone to arrange for the return or destruction of these documents.
was Hibernate4 integrator discovery tested on Tomcat7? I have two users reporting that they tried to use Hibernate 4 with Envers on Tomcat 7, and both have the same exception:
Servlet.service() for servlet Provider org.hibernate.envers.event.EnversIntegrator not found in context with path/jpaproy threw exception [org.hibernate.integrator.spi.Integrator:
Provider org.hibernate.envers.event.EnversIntegrator not found] with root cause
java.util.ServiceConfigurationError: org.hibernate.integrator.spi.Integrator: Provider org.hibernate.envers.event.EnversIntegrator not found
which would mean that the file in META-INF specifying the integrator is visible, but the class itself - not.