Anyone using a non JPA2 version of hibernate is unable to utilize the capabilities of the MassIndexer introduced in version 3.2 of search. At a cursory glance I can not determine a dependency of the new indexer on JPA2.
It would be very beneficial to make this available as utilizing hibernate search on existing application and manually indexing is obviously difficult with this new massindexer.
Also anyone who chooses to use a supported version of jboss is excluded from this functionality until most likely 2012.
If this is not possible i would appreciate an explanation of the dependencies the massindexer has on search 3.2.
Hibernate 3.3.X and any jboss server platform prior to 6.0.
I could help you to contribute a patch if you really need it. (Did you checkout the alternative mass indexing strategy?)
It would be quite easy to backport the patch I originally contributed as HSEARCH-218, because this was done just after 3.1.x so before the upgrade to newer Hibernate APIs; but if you take that patch, you'll likely want also all subsequent fixes; you can easily find them as they all mention "MassIndexer" in the title. (only was not using this name yet). So it might be easier to just move in the package from the latest snapshot and fix the very little changes you'll need to get it going with the older Hibernate Core.
I don't really understand why you can't upgrade Hibernate core in your app, JPA2 is backwards compatible; we could discuss that. Regarding customers, AFAIK they can pretty much ask for this kind of services.
I just checked with JBoss integration experts, they confirmed that the fact you're having a JPA1 application doesn't prevent you in any way to use JBossAS6 or more recent.
Thanks for your response. Just to clarify, Application Server 6 is still not available to subscription customers. Once it is a subscription release it will still be months before many can migrate. I completely understand the difference between ,org and .com but was suggesting the backport to allow anyone who is a jboss.com subscriber (pays for jboss). The latest version of jboss as that is supported by jboss.com is 5.1 which does not use the hibernate version that the mass indexer requires. So in short the mass indexer would be unavailable to anyone using (paid) supported version of jboss as.
Thanks for your suggestion on how to accomplish the backport, I have already implemented a solution for my project.
Sorry for the previous response it was not very clear. First tanks for pointing out where to search for massindexer in the title. My concern is not so much with JPA 2. People who pay for JBoss are stuck with app server 5.1 for some time to come. The mass indexer is a great addition to search, but has what i suspect was circumventable dependency on hibernate 3.2.
Adding the mass indexer to search 3.1.X would allow all of the people who are paying for a supported version of jboss to take advantage of this functionality.
As you mentioned, the mass indexer itself does not seem to be strictly tied to jboss 3.2 so this effort would be a big benefit for anyone using a supported version of the application server.
You make good points. This is the balance we constantly try and adjust between innovation and stability in our products. New features are made in our projects and being new we have less feedback and don't know how stable they are. It would be foolish to claim we can support them properly. We're putting an effort in trying to have a faster pace between newer releases and supported releases, so that people don't have to wait for too long for a feature.
We generally don't backport new features to products as it could endanger the stability and the backward compatibility of the platform. This feature is a good example. We have found several bugs since its introduction and have been fixing them over time.
That said, we do break that rule from time to time and on a case by case basis upon customer demand and we have backported features needed by our customers when we found them stable enough.
I see that you've implemented a solution in your project but if you still need the feature in, please open a customer ticket and email me (sanne at hibernate dot org) or Emmanuel (emmanuel at hibernate dot org). No guarantee but we will push in your direction.