[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4886) Update Hibernate Search to latest 3.1.x version

[Vitali Yemialyanchyk (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12488952#action_12488952 ] 

Vitali Yemialyanchyk commented on JBIDE-4886:
---------------------------------------------

I think, there is a sence to have these jars in our bundle, the reason is build correct console configuration - by default, cause if classes has hibernate-search annotations - console configuration should reflect this. Of cause it is possible to add these jars manually into the classpath... but what is happens in default case? 
As I think, this was a reason to bundle these jars. So there is a sence to save it - IMO.
I'm trying to reproduce situation and check what is happens.

> Update Hibernate Search to latest 3.1.x version
> -----------------------------------------------
>
>                 Key: JBIDE-4886
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4886
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Hibernate
>    Affects Versions: 3.1.0.M3
>         Environment: Windows 7, JDK 6, Eclipse 3.5
>            Reporter: Clement Denis
>            Assignee: Vitali Yemialyanchyk
>
> In the Hibernate perspective, when I try to open the session factory for my entities, I get the following exception :
> org.hibernate.search.SearchException: No document id in: com.test.entity.organisation.Organisation
> 	at org.hibernate.search.engine.DocumentBuilder.<init>(DocumentBuilder.java:98)
> 	at org.hibernate.search.impl.SearchFactoryImpl.initDocumentBuilders(SearchFactoryImpl.java:262)
> 	at org.hibernate.search.impl.SearchFactoryImpl.<init>(SearchFactoryImpl.java:94)
> 	at org.hibernate.search.impl.SearchFactoryImpl.getSearchFactory(SearchFactoryImpl.java:172)
> 	at org.hibernate.search.event.FullTextIndexEventListener.initialize(FullTextIndexEventListener.java:44)
> 	at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:356)
> 	at org.hibernate.cfg.Configuration.getInitializedEventListeners(Configuration.java:1304)
> 	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294)
> 	at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
> 	at org.hibernate.console.ConsoleConfiguration$3.execute(ConsoleConfiguration.java:505)
> 	at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64)
> 	at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:94)
> 	at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:500)
> 	at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
> 	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
> 	at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> 	at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> It's because the hibernate search jar provided with the plugin is the 3.0 version, and needs entities to be annotated with @DocumentId. These entities work fine in my appplication with the latest versions of hibernate and hibernate search (3.1.1).
> As a workaround, I removed the hibernate-search.jar and lucene-core.2.2.0.jar from plugins\org.hibernate.eclipse_3.3.0.v200909110340M-H277-M3\lib\annotations, and added manually the latest versions in the classpath of the hibernate launch configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira