]
Sanne Grinovero resolved HSEARCH-949.
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.0.0.Final)
4.0.0.CR2
Update online documentation
---------------------------
Key: HSEARCH-949
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-949
Project: Hibernate Search
Issue Type: Task
Components: documentation
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Fix For: 4.0.0.CR2
In articular the architecture and configuration chapters need updating after the
extensive 4.0 refactoring.
The idea is to move the _IndexManager_ into the center.
from hibernate-dev mailing list
{quote}
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.default.xyz are default values which apply
for any index manager if
not overridden explicitly
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: