[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-728) Backport MassIndexer to 3.1.X

[Chris Hornsey (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42947#comment-42947 ] 

Chris Hornsey commented on HSEARCH-728:
---------------------------------------

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.

> Backport MassIndexer to 3.1.X
> -----------------------------
>
>                 Key: HSEARCH-728
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-728
>             Project: Hibernate Search
>          Issue Type: Task
>          Components: massindexer
>    Affects Versions: 3.1.1.GA
>         Environment: Hibernate 3.3.X and any jboss server platform prior to 6.0.
>            Reporter: Chris Hornsey
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira