|
|
|
It was the gzipFilter, disable it then we are good.
I found that the ehcache is still 1.2.3 even in RC1-SNAPSHOT. Is there a reason not to upgrade to 1.3.0-beta like the others? We did upgrade the GZipFilter to 1.3.0-beta2 recently. Can you build your project with "mvn package -X | tee mvn.log" and look at mvn.log to ensure this is the version being used?
I've checked, if I delete ehcache form local m2 repo, it keeps downloading ehcache 1.2.
It looks like1.3.0-beta2 is not in any maven repos, that's why maven fall back to 1.2.3, that's what hibernate 3.2.1.ga depends. The folllowing log can confirm that: [DEBUG] net.sf.ehcache:ehcache:jar:1.3.0-beta2:compile (removed - nearer found: 1.2.3) Alfter a little bit googling, I found that ehcache 1.3.0-beta3 is released in May 27, then beta2 is removed from repo.
That's why this issue only came out today I was wrong, 1.3.0-beta2 is in the repo, maven just didn't get it.
In the current situation we end up have both ehcache-1.2.3.jar and ehcache-1.3.0-beta.jar in the WEB-INF/lib, but not ehcache-1.3.0-beta2.jar Check the mvn.log for detail. More info.
This issue only affects basic artifacts, I think it is because ehcache dependency only defined in appfuse-service*.pom. I tried moving ehcache dependency to appfuse*.pom then problems all gone. Fixed by excluding ehcache from hibernate dependency and including AppFuse's version.
https://appfuse.dev.java.net/source/browse/appfuse/trunk/data/hibernate/pom.xml?view=diff&rev=2787&p1=trunk/data/hibernate/pom.xml&p2=trunk/data/hibernate/pom.xml&r1=2786&r2=2787 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This is pretty weird, because if you do the "view source", all charaters looks ok.
jsf and spring are not affected.