[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-182) Use Directory getLockID() to uniquely identify a directory provider

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard updated HSEARCH-182:
-------------------------------------

    Fix Version/s:     (was: 3.1.0.Beta1)

Does not seem to fly las I recalled.

> Use Directory getLockID() to uniquely identify a directory provider
> -------------------------------------------------------------------
>
>                 Key: HSEARCH-182
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-182
>             Project: Hibernate Search
>          Issue Type: Improvement
>          Components: directory provider
>            Reporter: Emmanuel Bernard
>            Priority: Minor
>
> Today the DirectoryProvider needs to implement equals and hashCode so that the underlying Directory is unique.
> We could delegate that to the directory.getLockID() which seem to fulfill the same contract.
> Not sure it works well with our lazy initialization strategy though. This needs to be checked out.

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira