[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-429) Add a configuration property to declaratively use a factory for the programmatic mapping API

Sanne Grinovero (JIRA) noreply at atlassian.com
Wed Dec 2 08:39:23 EST 2009


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

Sanne Grinovero commented on HSEARCH-429:
-----------------------------------------

Right that would be really useful. I hacked an experiment to implement this when you started with programmatic API, as I needed the EMF to be provided and managed by the container.

> Add a configuration property to declaratively use a factory for the programmatic mapping API
> --------------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-429
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-429
>             Project: Hibernate Search
>          Issue Type: New Feature
>            Reporter: Emmanuel Bernard
>             Fix For: 3.2.0.Beta3
>
>
> The current model when using the  programmatic mapping API is to pass the instance of SearchMapping to the Configuration object. This is not possible in simple environments when Hibernate bootstrapping is done automatically.
> hibernate.search.mapping_factory com.acme.SearchMappingFactory
> could be used.
> Either the SearchMappingFactory class implements a MappingFactory.getMapping() interface
> or we look for a @Factory annotation on the class methods.
> TODO think about injection and how to get external info.

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