Re: camel-cache: Using Objects for cache

Thanks Ashwin, EHCache has MBean which exposes all the statistics. I guess, for now I can just expose it myself to mbean server. Thanks for all the help :) Ashwin Karpe wrote: > > Hi, > > The other request regarding exposing cache statistics is a little more > involved. > > I have created a

Re: camel-cache: Using Objects for cache

Hi, The other request regarding exposing cache statistics is a little more involved. I have created a Jira entry for it and will try and add this feature in due course. Cheers, Ashwin... tide08 wrote: > > Thanks Claus! ArtifactID says springsource is it some customized version > of ehCache

Re: camel-cache: Using Objects for cache

Hi Claus, I fixed the sample cache creation issue and have checked in a patch CAMEL-2363. Cheers, Ashwin... Claus Ibsen-2 wrote: > > On Wed, Jan 13, 2010 at 7:19 PM, tide08 wrote: >> >> Thanks Claus! ArtifactID says springsource is it some customized version >> of >> ehCache we are using?

Re: camel-cache: Using Objects for cache

Hi, No problem. I will clean out the other caches... I did not realize that these were not commented out :) Cheers, Ashwin tide08 wrote: > > Thanks Claus! ArtifactID says springsource is it some customized version > of ehCache we are using? Reason I am asking is that I have conflict with

Re: camel-cache: Using Objects for cache

Hi, The version of ehCache used by camel-cache is 1.6.2. This can however be modified to an earlier or later version. Cheers, Ashwin... tide08 wrote: > > Looks like Ashwin got on to this before I could submit mine. > > BTW..what version of ehCache does it use? It is not very clear from pom

Re: camel-cache: Using Objects for cache

Hi, The version of ehCache used is 1.6.2. This is however modifiable to a later or earlier version. Cheers, Ashwin... tide08 wrote: > > Looks like Ashwin got on to this before I could submit mine. > > BTW..what version of ehCache does it use? It is not very clear from pom > (and osgi is ne

Re: camel-cache: Using Objects for cache

On Wed, Jan 13, 2010 at 7:19 PM, tide08 wrote: > > Thanks Claus! ArtifactID says springsource is it some customized version of > ehCache we are using? Reason I am asking is that I have conflict with > hibernate and I need to exclude ehCache dependency from either one of these. > Its the OSGi prob

Re: camel-cache: Using Objects for cache

Thanks Claus! ArtifactID says springsource is it some customized version of ehCache we are using? Reason I am asking is that I have conflict with hibernate and I need to exclude ehCache dependency from either one of these. Also, I had another suggestion for cache component: - Clean up ehCache.xm

Re: camel-cache: Using Objects for cache

On Wed, Jan 13, 2010 at 12:32 AM, tide08 wrote: > > Looks like Ashwin got on to this before I could submit mine. > > BTW..what version of ehCache does it use? It is not very clear from pom (and > osgi is new to me) > Check the parent/pm.xml which have versions listed. Otherwise do a mvn dependen

Re: camel-cache: Using Objects for cache

Looks like Ashwin got on to this before I could submit mine. BTW..what version of ehCache does it use? It is not very clear from pom (and osgi is new to me) Thanks! tide08 wrote: > > Thanks! I will reply back when patch is ready. > > > > Claus Ibsen-2 wrote: >> >> Hi >> >> I created a ti

Re: camel-cache: Using Objects for cache

Thanks! I will reply back when patch is ready. Claus Ibsen-2 wrote: > > Hi > > I created a ticket for it > https://issues.apache.org/activemq/browse/CAMEL-2343 > > On Wed, Jan 6, 2010 at 6:12 AM, Claus Ibsen wrote: >> On Wed, Jan 6, 2010 at 3:44 AM, Willem Jiang >> wrote: >>> I think we ca

Re: camel-cache: Using Objects for cache

Hi I created a ticket for it https://issues.apache.org/activemq/browse/CAMEL-2343 On Wed, Jan 6, 2010 at 6:12 AM, Claus Ibsen wrote: > On Wed, Jan 6, 2010 at 3:44 AM, Willem Jiang wrote: >> I think we can support the InputStream and Serializable object at the same >> time :) >> If the Message b

Re: camel-cache: Using Objects for cache

On Wed, Jan 6, 2010 at 3:44 AM, Willem Jiang wrote: > I think we can support the InputStream and Serializable object at the same > time :) > If the Message body is Serializable, we can skip the InputStream part, if > it's not, we can try to turn it into an InputStream. > > Any thought? > Yeah my

Re: camel-cache: Using Objects for cache

I think we can support the InputStream and Serializable object at the same time :) If the Message body is Serializable, we can skip the InputStream part, if it's not, we can try to turn it into an InputStream. Any thought? BTW, any kind of contribution is welcome, so please feel free to submit