[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-1108) programmatic API doesn't work correctly for entities with @MappedSuperclass parent
Sanne Grinovero (JIRA)
noreply at atlassian.com
Thu Apr 26 05:10:50 EDT 2012
[ https://hibernate.onjira.com/browse/HSEARCH-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero updated HSEARCH-1108:
-------------------------------------
Suitable for new contributors: [Yes, likely]
Labels: candidate_for_next programmatic (was: programmatic)
> programmatic API doesn't work correctly for entities with @MappedSuperclass parent
> ----------------------------------------------------------------------------------
>
> Key: HSEARCH-1108
> URL: https://hibernate.onjira.com/browse/HSEARCH-1108
> Project: Hibernate Search
> Issue Type: Bug
> Components: mapping
> Affects Versions: 4.0.0.Final, 4.1.0.Final
> Environment: HibernateCore 4.1.2, HSearch 4.1.0, Glassfish3 (JPA) or even as a standalone java app
> Reporter: David Janca
> Labels: candidate_for_next, programmatic
>
> The hibernate search configuration specified by programmatic API (SearchMapping class) is ignored for entities that have @MappedSuperclass parent.
> All fields that are declared in a @MappedSuperclass parent are not recognized by programmatic config and ignored (when configured like this: mapping.property("property", ElementType.FIELD)).
> We've already found a workaround for this problem - to overwrite getter method in @Entity class (just calling super.getter) and configure it like following: mapping.property("property", ElementType.METHOD). But I think that's not the real solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list