[
https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.pl...
]
Arsen Torbarina commented on JBSEAM-4454:
-----------------------------------------
Are there any side-effects if @org.jboss.seam.annotations.intercept.PostConstruct is
replaced with @javax.ejb.PostConstruct? What about pre Java EE 5 envirnoments?
On the other hand, there are also other core classes that use javax.ejb.PostConstruct
directly, like the SessionBeanInterceptor and TimeServiceDispatcher, so it shouldn't
make any difference, right?
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: 2.2.1.CR1
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