Made a note on the release notes:
Hibernate 3.2.0.CR2 works with the latest ehcache v1.2 but not with
previous versions. JBoss Portal v2.2.1 will fail to deploy on JBoss
4.0.4.GA unless ehcache gets upgraded to v1.2.
-Original Message-
From: Scott M Stark
Sent: 13 May, 2006 18:14
Because:
- this is a minor release increase (not a micro) for Hibernate
- we always stay up-to-date with our third party libraries
- EhCache had a major cache design flaw that was fixed in
1.2 (use to keep the cache manager as a singleton)
- we do not keep outdated cache provider, but
I have upgraded branch 2.2 with ehcache 1.2 for releasing an SP1.
Dimitris Andreadis wrote:
So we either bundle the new version of ehcache or hibernate needs
fixing?
-Original Message-
From: Scott M Stark
Sent: 13 May, 2006 17:28
To: Roy Russo; Julien Viet; Ryan Campbell
Cc: Adrian
Because:
- this is a minor release increase (not a micro) for Hibernate
- we always stay up-to-date with our third party libraries
- EhCache had a major cache design flaw that was fixed in 1.2 (use to
keep the cache manager as a singleton)
- we do not keep outdated cache provider, but people can
Title: Re: jboss-4.0.4 portal-2.2 issue
Upgrade ehcache to 1.2
-Original Message-
From: Ryan Campbell
To: Steve Ebersole; Julien Viet; Roy Russo
CC: 'jboss-development@lists.sourceforge.net' jboss-development@lists.sourceforge.net; QA
Sent: Fri May 12 13:05:28 2006
But why that incompatibility (not working with older ehcache) was
introduced in hibernate?
-Original Message-
From: Emmanuel Bernard [mailto:[EMAIL PROTECTED]
Sent: 13 May, 2006 20:26
To: Roy Russo
Cc: Scott M Stark; Dimitris Andreadis; Julien Viet; Ryan
Campbell; Adrian Brock;
Any of those change requires a SP, so it's better to upgrade (Julien did
it :) )
Dimitris Andreadis wrote:
Because:
- this is a minor release increase (not a micro) for Hibernate
- we always stay up-to-date with our third party libraries
- EhCache had a major cache design flaw that was
I thought if javap showed no ctor this implied a public default ctor,
but this is not the case. This version of ehcache has no public ctor so
the 3.2.0.CR2 hibernate is simply incompatible with this earlier version
of ehcache. This is a change introduced between 3.2.0.CR1 and 3.2.0.CR2?
So we either bundle the new version of ehcache or hibernate needs
fixing?
-Original Message-
From: Scott M Stark
Sent: 13 May, 2006 17:28
To: Roy Russo; Julien Viet; Ryan Campbell
Cc: Adrian Brock; Steve Ebersole;
'jboss-development@lists.sourceforge.net'; QA; Rali Genova
We need to document the incompatibility in the release notes and either
create an sp release of portal with an updated ehcache, or one that uses
jboss cache. What is the reason for using ehache?
-Original Message-
From: Dimitris Andreadis
Sent: Saturday, May 13, 2006 7:53 AM
To: Scott M
the reason we use cache is performance :-)
the best idea is to issue a 2.2.1 SP 1 with an upgraded cache.
Roy Russo wrote:
Julien can explain that. How is this going to affect people doing
something like we do in portal?
This isnt just a portal issue to me.
STAY METAL!
Roy Russo
JBoss
11 matches
Mail list logo
