[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-397) Allow classes to be lazily added to the configuration

Emmanuel Bernard (JIRA) noreply at atlassian.com
Wed Oct 21 14:09:27 EDT 2009


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

Emmanuel Bernard commented on HSEARCH-397:
------------------------------------------

-1 this is not moving to 3.2 unless you are absolutely certain to carry it over by yourself. It's an important concurrency rework that we agreed to delay to post 3.2 last I talked to Manik

> Allow classes to be lazily added to the configuration
> -----------------------------------------------------
>
>                 Key: HSEARCH-397
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-397
>             Project: Hibernate Search
>          Issue Type: New Feature
>          Components: engine
>            Reporter: Emmanuel Bernard
>            Assignee: Sanne Grinovero
>             Fix For: 3.2.0
>
>
> Assigning Sanne to pick his interest ;)
> Infinispan needs a way to add new classes lazily, ie after the SearchFactory initialization. Today's initialization cannot ensure that because we assume a single thread inits everything before freezing the state and then support multiple thread.
> We need to explore the idea of making the configuration mutable but not suffering too much of the thread-safety implications.
> We also should allow to remove a class from the configuration.

-- 
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

        


More information about the hibernate-issues mailing list