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

Flavio Costa (JIRA) jira-events at lists.jboss.org
Fri Mar 26 02:01:37 EDT 2010

    [ https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12522185#action_12522185 ] 

Flavio Costa commented on JBSEAM-4454:

Can't this be fixed for 2.2.1.CR2?
Seems rather simple.

> HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
> --------------------------------------------------------------------------------
>                 Key: JBSEAM-4454
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4454
>             Project: Seam
>          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
>             Fix For: The future
>   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.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list