Open GoogleCodeExporter opened 9 years ago
Do you have any version Ehcache on you classpath?
Original comment by eric.dalquist
on 14 Sep 2010 at 12:22
Haven't heard back from reporter. I'm going to assume this is a deployment
configuration issue.
Original comment by eric.dalquist
on 15 Sep 2010 at 7:24
Sorry, I didn't get chance to look at the issue today as I was trying to figure
out what was wrong and find a caching solution.
Your library doesn't just want a version of ehcache on the class path, it's
manifest specifies imports of 2 ehcache packages in it's manifest. When
specifying the packages it specifies the version as between 2.0.0 and 3.0.0.
The only OSGi compatible version of ehcache is 1.6.2 and is the spring wrapped
bundle. Ehcache-spring-annotations specifies an unsatisfiable depenedcy. It
also doesn't seem possible to use pax to wrap the maven dependencyof
ehcache-core 2.1
Original comment by benjamin...@gmail.com
on 15 Sep 2010 at 8:12
I also wasn't notified by email of your comments, just of you setting the bug
as invalid. You should probably leave a bit more time for people to respond.
Original comment by benjamin...@gmail.com
on 15 Sep 2010 at 8:15
Sorry about the quick close.
You can take a look at
http://code.google.com/p/ehcache-spring-annotations/issues/detail?id=31 for the
reasoning behind the current OSGI configuration.
Note that neither myself or the other developer on this project use OSGI and
the current manifest configuration is completely based on what was provided in
Issue 31.
If you have a patch that would address your issue please provide it.
Original comment by eric.dalquist
on 15 Sep 2010 at 8:57
I'll see what Ican do. After debugging the problem I have a good knowledge of
the problem area, here's hoping for a quick fix.
Original comment by benjamin...@gmail.com
on 15 Sep 2010 at 9:08
Any more updates on this issue? We'd love to have better OSGI support if
someone with OSGI experience can give us a hand.
Original comment by eric.dalquist
on 25 Oct 2010 at 4:27
We are having the same problem with Spring DM Server. Any update on this?
Original comment by pdur...@gmail.com
on 26 Oct 2010 at 7:56
Like I said earlier in this issue, Nick and I do not use OSGi and are not
familiar with the technology. If someone out there is an OSGi expert and can
provide us a patch to address these issues we'll be happy to apply it.
Original comment by eric.dalquist
on 26 Oct 2010 at 11:25
Hi,
Sorry I have made no progress on this issue at the moment. I am in the middle
of a busy and time pressured project, but I do hope to get to the bottom of
this at some point. I will do my best to get an update as soon as possible.
Ben.
Original comment by benjamin...@gmail.com
on 27 Oct 2010 at 8:08
According to some of the other posts, ehcache 1.6.0+ will work for this
project. If this is true, there is an existing OSGI net.sourceforge.ehcache
bundle for version 1.6.2. I believe that changing this project's manifest file
import statement to contain something like this:
Import-Bundle: com.springsource.net.sf.ehcache;version="[1.6.2,1.6.2]"
should do the trick.
Original comment by pdur...@gmail.com
on 9 Nov 2010 at 2:57
I've got a similar problem. In a non-osgi environment, websphere application
server still uses the manifest file to load dependend jars.
The solution I have created, is to fix the manifest.mf file of the
spring-context-support.2.5.6.SEC02.jar.
In that file there is a reference to net.sf.ehcache to version [1.0.0,2.0.0).
But ehcache-core-2.1.0.jar does not have a version in his manifest file, and it
is greater then the maximum version. For websphere, my quickfix was to create
an almost empty manifest file for spring-context-support.2.5.6.SEC02.jar. For
an osgi environment, it would be nice to create a correct manifest file for
ehcache-core.jar. And to fix the dependency in
spring-context-support.2.5.6.SEC02.jar
Original comment by robrecht...@gmail.com
on 19 Jan 2011 at 4:00
Attachments:
Any update on this issue.
Original comment by maniksan...@gmail.com
on 3 May 2012 at 10:55
Original issue reported on code.google.com by
benjamin...@gmail.com
on 14 Sep 2010 at 11:12