You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by lmanchanda75 <lm...@gmail.com> on 2013/09/01 19:11:51 UTC
camel cache
Hi,The camel cache implementation which provides an ehcache integration
component forces a serializable object though ehcache allows
non-serializable objects too if clustering is not required. This makes in
unusable for some scenarios. Any specific reason for doing so?Regdslalit
--
View this message in context: http://camel.465427.n5.nabble.com/camel-cache-tp5738435.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel cache
Posted by lmanchanda75 <lm...@gmail.com>.
Hi Claus,
I have created the following Jira ticket.
https://issues.apache.org/jira/browse/CAMEL-6698
Will work to do the improvement and submit.
Regds
lalit
--
View this message in context: http://camel.465427.n5.nabble.com/camel-cache-tp5738435p5738509.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel cache
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
There is no specific reason. We welcome contributions so feel free to
log a JIRA and if possible provide a patch with this improvement.
http://camel.apache.org/contributing.html
On Sun, Sep 1, 2013 at 7:11 PM, lmanchanda75 <lm...@gmail.com> wrote:
> Hi,The camel cache implementation which provides an ehcache integration
> component forces a serializable object though ehcache allows
> non-serializable objects too if clustering is not required. This makes in
> unusable for some scenarios. Any specific reason for doing so?Regdslalit
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-cache-tp5738435.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen