[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-444) Search fails to start when core uses XML mappings making use of entity-name attribute
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-444?pag...
]
Emmanuel Bernard commented on HSEARCH-444:
------------------------------------------
I can get it to work (in some cases) but I need to understand the reasons why you are
using an entity-name.
Are you keeping a 1-1 relationship between an entity-name and a class or are you using
entity names to map the same class multiple times.
If the later can you explain your use case?
If the former, well can you explain your reason?
The current "easy" patch bind an entity-name to a class and is half done (though
will require more work on the DocumentBuilder and DocumentExtractor. That will work if we
keep a 1-1 relationship
I wonder if we can make the second approach work (ie the same class mapped multiple times
via entity-names). That's definitively a harder problem that I am not willing to fight
without a justified use case :)
Search fails to start when core uses XML mappings making use of
entity-name attribute
-------------------------------------------------------------------------------------
Key: HSEARCH-444
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-444
Project: Hibernate Search
Issue Type: Bug
Components: mapping
Affects Versions: 3.1.0.GA
Reporter: Sanne Grinovero
Assignee: Emmanuel Bernard
Fix For: 3.2.0.Beta2
As described on forums: https://forum.hibernate.org/viewtopic.php?f=9&t=993687
classes mapped using XML on hibernate core, like
classes starting with:
<class name="com.mydomain.myapp.AnswerImpl" table="answer"
entity-name="Answer">
cause:
Caused by: java.lang.NullPointerException
at
org.hibernate.search.cfg.SearchConfigurationFromHibernateCore.getClassMapping(SearchConfigurationFromHibernateCore.java:31)
at
org.hibernate.search.store.DirectoryProviderFactory.getDirectoryProviderName(DirectoryProviderFactory.java:226)
at
org.hibernate.search.store.DirectoryProviderFactory.createDirectoryProviders(DirectoryProviderFactory.java:53)
at
org.hibernate.search.impl.SearchFactoryImpl.initDocumentBuilders(SearchFactoryImpl.java:404)
at org.hibernate.search.impl.SearchFactoryImpl.<init>(SearchFactoryImpl.java:119)
at
org.hibernate.search.event.ContextHolder.getOrBuildSearchFactory(ContextHolder.java:30)
at
org.hibernate.search.event.FullTextIndexEventListener.initialize(FullTextIndexEventListener.java:59)
at org.hibernate.event.EventListeners$1.processListener(EventListeners.java:198)
at org.hibernate.event.EventListeners.processListeners(EventListeners.java:181)
at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:194)
... 16 more
This was reported on 3.1.0.GA but I guess it affects all releases.
There's a "test WAR" in the forums, going to ask for a testcase.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira