[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
9:50 a.m.
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.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1
Reporter: Arsen Torbarina
Fix For: 2.2.1.CR1
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.
--
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
10 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.pl...
]
Arsen Torbarina updated JBSEAM-4454:
------------------------------------
Description:
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.
was:
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.
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
10:16 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
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
11:39 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.pl...
]
Flavio Costa commented on JBSEAM-4454:
--------------------------------------
I came across the same bug and was introduced due to another bug here: JBSEAM-4093. /
r10535.
The WILDCARD_AS_COUNT_QUERY_SUBJECT really stopped working, using Hibernate does not make
a difference, because, like Arsen said, the init() method is never called.
My workaround was to create a component with the same name, the "correct"
annotation (javax.annotation.PostConstruct) and a higher precedence.
Solutions are reverting revision 10535 (breaking Websphere), advise Websphere users to
drop the needed jars with the correct annotations or create a different component that
only gets installed when Websphere is detected (worst solution imho).
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
12:04 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.pl...
]
Arsen Torbarina commented on JBSEAM-4454:
-----------------------------------------
Thanks, Flavio, for your point.
However, putting the seam.PostConstruct at the init() does not get any job done, since it
never executes. And it should, in order to perform the initialization of the component,
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
2:24 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-4454:
------------------------------------
Fix Version/s: The future
(was: 2.2.1.CR1)
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
1:01 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://jira.jboss.org/jira/browse/JBSEAM-4454?page=com.atlassian.jira.pl...
]
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
1:16 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://issues.jboss.org/browse/JBSEAM-4454?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4454:
----------------------------------
Assignee: Marek Novotny
Fix Version/s: 2.3.0.ALPHA
(was: The future)
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.ALPHA
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
8:53 a.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://issues.jboss.org/browse/JBSEAM-4454?page=com.atlassian.jira.plugi...
]
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
9:41 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://issues.jboss.org/browse/JBSEAM-4454?page=com.atlassian.jira.plugi...
]
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
https://issues.jboss.org/browse/JBSEAM-3726?focusedCommentId=12442959&...
and
https://issues.jboss.org/browse/JBSEAM-3726?focusedCommentId=12460472&...
.
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: http://www.atlassian.com/software/jira
1:38 p.m.
New subject: [JBoss JIRA] (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://issues.jboss.org/browse/JBSEAM-4454?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-4454:
---------------------------------------
Please provide test case. Otherwise I will reject the issue. The problem to not follow
change back to EJB annotations is clear from
https://issues.jboss.org/browse/JBSEAM-3726?focusedCommentId=12460472&...
So if you are affected by not setting of
HibernatePersistenceProvider.supportsFeature(Feature.WILDCARD_AS_COUNT_QUERY_SUBJECT),
there is obviously different cause.
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:02 p.m.
New subject: [JBoss JIRA] (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing
[
https://issues.jboss.org/browse/JBSEAM-4454?page=com.atlassian.jira.plugi...
]
Marek Novotny updated JBSEAM-4454:
----------------------------------
Fix Version/s: (was: 2.3.0.BETA1)
moving into Unscheduled issues since no reproducing test case exists
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
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4524
days inactive
5336
days old
11 comments
5 participants
participants (5)
-
Arsen Torbarina (JIRA) -
Flavio Costa (JIRA)
-
Marek Novotny (Commented) (JIRA)
-
Marek Novotny (JIRA)
-
Norman Richards (JIRA)