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

Sanne Grinovero (JIRA) noreply at atlassian.com
Tue Sep 8 08:41:16 EDT 2009


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

Sanne Grinovero commented on HSEARCH-397:
-----------------------------------------

yes, interesting.
The configuration building was needing an update anyway: what do you think in making SearchFactoryImpl completely immutable, and replace the reference with a new one?
To make it immutable we need a factory, and this factory could also have a method to create a new one basing on an existing one, just changing for example the indexed classes.
(changing in the sense that the new one will have some differences with the previous, not changing the instance itself).

After having built the new instance we could replace the existing in FullTextIndexEventListener, or wherever the reference should live.
Introducing a factory for a SearchFactoryImpl is calling for some namechanges.

> 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

        


More information about the hibernate-issues mailing list