Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5C93118BF3 for ; Thu, 23 Apr 2015 11:34:39 +0000 (UTC) Received: (qmail 73153 invoked by uid 500); 23 Apr 2015 11:34:39 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 73105 invoked by uid 500); 23 Apr 2015 11:34:39 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 73090 invoked by uid 99); 23 Apr 2015 11:34:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Apr 2015 11:34:39 +0000 Date: Thu, 23 Apr 2015 11:34:38 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CAMEL-8681) Camel-Infinispan: use Lifespan and Max Idle Time in the implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-8681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8681. -------------------------------- Resolution: Fixed > Camel-Infinispan: use Lifespan and Max Idle Time in the implementation > ---------------------------------------------------------------------- > > Key: CAMEL-8681 > URL: https://issues.apache.org/jira/browse/CAMEL-8681 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan > Reporter: Andrea Cosentino > Assignee: Willem Jiang > Priority: Minor > Fix For: 2.16.0 > > > In Camel-infinispan we don't use Lifespan and Max Idle Time variable when we put a key/value pair in an Infinispan cache. > There are some methods that use this variables and I think we have to change the implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)