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

[Emmanuel Bernard (JIRA)]

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

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

actually, the problem with your approach is that it requires to re reference the SF in whatever listener is using them. which can be pain.
Maybe having a delegator SF that can do the switch would be preferable.
BTW if we can remove classes from a SF, then sharing things like the indexing queue and the DProviders might be problematic. not sure

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