[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing

Marek Novotny (JIRA) jira-events at lists.jboss.org
Mon Jul 25 09:53:23 EDT 2011

     [ https://issues.jboss.org/browse/JBSEAM-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-4454:

    Fix Version/s: 2.3.0.BETA1
                       (was: 2.3.0.ALPHA)

> HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
> --------------------------------------------------------------------------------
>                 Key: JBSEAM-4454
>                 URL: https://issues.jboss.org/browse/JBSEAM-4454
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.CR1, 2.1.2.CR2, 2.1.2.GA, 2.2.0.CR1, 2.2.0.GA
>            Reporter: Arsen Torbarina
>            Assignee: Marek Novotny
>              Labels: HibernatePersistenceProvider, PersistenceProvider, PostConstruct
>             Fix For: 2.3.0.BETA1
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> Method org.jboss.seam.persistence.PersistenceProvider.init() (including its subclass' method HibernatePersistenceProvider.init()) never gets executed, because it is annotated with @org.jboss.seam.annotations.intercept.PostConstruct instead of @javax.ejb.PostConstruct.
> BTW, this is the root cause why EntityQuery breaks on MySQL when counts entities with composite keys. The method EntityQuery.validate() should setUseWildcardAsCountQuerySubject according to the HibernatePersistenceProvider.supportsFeature(Feature.WILDCARD_AS_COUNT_QUERY_SUBJECT), but the latter always returns false, because HibernatePersistenceProvider.init() that sets the feature flag is never executed.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list