I am using Hibernate Annotiations, EntityManager, and JPA, and I have data in my database. When I attempt to manually index my database, I get the following:




Here are my property settings in persistence.xml:



Here is the indexing code:



I would appreciate any insight into what configuration setting I am missing here.

As a side note, and I know this is a JPA thing, but any insight as to how em.createQuery can return a collection of Items through generics would be appreciated as well.

Thanks.

I think you need to set up org.hibernate.search.event.FullTextIndexEventListener's

See http://www.hibernate.org/hib_docs/searc ... le/#d0e874[code][/code]

Thanks. I saw that myself when I was doing my research, but I found this line:

"To enable Hibernate Search in Hibernate Core, add the FullTextIndexEventListener for the three Hibernate events that occur after changes are executed to the database. Once again, such a configuration is not useful with Hibernate Annotations or Hibernate EntityManager."

As I mentioned before, I am using JPA as an abstraction to Hibernate. I am not even sure how I would set those listeners in persistence.xml. But even still, I think the above means that that may not be the answer.

Of course, it is better than anything else I have come up with to this point!

Thanks again.

It seems you are using a older version of Hibernate annotations.
You need version 3.3.x to have the transparent integration. I bet you're using 3.2.x

Actually, because my project is using Seam, I am using all the Hibernate libraries, including Search, that come with Seam 2.0 GA. I took a look at hibernate-annotations.jar, and here is the manifest file:




Here is the manifest file from hibernate-commons-annotations.jar:




Finally, here is the manifest file from hibernate-entitymanager.jar:




Let me know if I can provide any more information.

Thanks.

Are you using Seam inside JBoss AS?
Which version?

No, all I am doing at the moment is running a TestNG test outside the container of my search class, which does things like use the Lucene query API to produce a query from user-provided values for an "advanced search" capability and generate results. (Sadly, I will be running on WL 9.2 and not JBoss, but that is just FYI and irrelevant to this discussion.)

The exception that I described is thrown in my test fixture setup method. Prior to the method call, DBUnit populates my database with known data. Then in my fixture setup method, I bootstrap an entity manager and do a "manual" index of the one table I will be searching on as shown in the code I provided in my initial message. It is just as I attempt to index the first item that I get that exception.

Please let me know what else I can provide. I am very excited about Hibernate Search, but this issue is really delaying my progress right now.

Thanks.

I have found when I run a SeamTest class in TestNG that it is easy to forget to supply something in your test fixture that would automatically be supplied by the container. The test fails as a result, and it is always really hard to determine why. Any insight you can provide as to something I may be missing in my persistence.xml would be helpful.

Incidentally, what are all the possible causes of the "Hibernate Search Event listeners not configured" error?

Thanks.

So I traced through the Hibernate Search source to see if I can figure anything out about this error. A couple of observations:

1) From the stack trace:



The bottom line provided means I am certainly using Hibernate entity manager and JPA. And as it says in the documentation,

"Hibernate Search is enabled out of the box when using Hibernate Annotations or Hibernate EntityManager."

So this suggests I shouldn't need to do anything involving listeners if I am using either of those correctly.


2) Here is the Hibernate Search method in org.hibernate.search.util.ContextHelper that throws the exception:



The SessionImplementor object should have an array of PostInsertEventListeners, but the array is empty. I see how to provide such a thing in the documentation. However, that is supposed to be unnecessary with Hibernate EntityManager. Furthermore, I am unaware how to do the following in a JPA persistence.xml file:




Anyway, so I have done my homework, and it seems like either there is a bug in the code, or more likely I am missing a simple item in my persistence.xml, or even more likely I am failing to bootstrap something for TestNG in my SeamTest.

If Emmanuel or his team could speak to those possibilities, or if anyone has actually written a TestNG class to test their queries before deploying them, I would appreciate some insight.

Thanks.

Well, at the very least, I did figure out how to add listeners in persistence.xml--courtesy of the "dvdstore" sample in the Seam 2.0 GA distribution.

Here it is:



Of course, the above is preceded by the following comment:



As I mentioned in a previous message, I am indeed using HA 3.3. But you can't believe everything you read. Right, Matt Drudge?

At this point, my next steps are to make sure there isn't some sort of JAR file collision and to simply add these explicitly to my persistence.xml and see what happens.

Any insight or thoughts are encouraged.

Thanks.

I am almost certain this is indeed some jar collision, you most likely have 2 Hibernate Annitations jars or 2 hibernate-entitymanger jars in your classpath (or one of the hibernate-all ish bundle).

It turns out that we were both right. I had a stray hibernate-all.jar in my classpath, and clearly that was causing a bad collision. Once I removed it, the indexing process began nicely. I did find this:



But I cannot remember the last time I was so happy to see an exception!

I will study the documentation and start a new thread if I can't figure this one out on my own, but I appreciate the guidance on this listener issue.

Thank you, Emmanuel.

Hmm ... I have the exact problem at the moment. I checked for JAR collision and I'm pretty sure everything's ok. I even deleted my project and recreate and carefully copy only required JARs. As for the JAR versions, I've just downloaded the latest Core, Annotations and Search so I guess it shouldn't be a problem. My xml configuration is exactly the same as the one posted in the first post.

I read from http://forum.hibernate.org/viewtopic.ph ... configured that 3 XML lines are not required. (I tested with and without anyway).

Below are my file versions, please let me know what I'm doing wrong.

hibernate-annotations-3.4.0.GA
hibernate-distribution-3.3.0.SP1
hibernate-search-3.0.1.GA

As for Lucene, I'm using the lucene-core-2.3.0.

Can someone enlighten me on what I did wrong? I've been searching and searching and I still haven't got my answer.

Hmm .. The exception is gone after I changed the listeners configurations to

<listener type="post-insert" class="org.hibernate.search.event.FullTextIndexEventListener"/>
<listener type="post-update" class="org.hibernate.search.event.FullTextIndexEventListener"/>
<listener type="post-delete" class="org.hibernate.search.event.FullTextIndexEventListener"/>

No idea whether it really indexed though. Checked the index folder and there are some files there.

Hi,

even i have the same problem with my project.

what solution you have posted, i have tried that even but no success.

can you please explain your persistence.xml

your help would be appreciable :)