]
Marek Novotny commented on JBSEAM-4454:
---------------------------------------
What is the reproducer case?
As you might read related jira issue JBSEAM-3726, which is root of changing annotation
from EJB3 one to Seam annotations, the bug was in Seam methods signature. See at
.
I need to see a test case to reproduce it and fix it properly. Changing back to wrong
state is not a way how to fix it.
I hope you understand my concerns, thanks!
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: