Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2B787200B7A for ; Mon, 5 Sep 2016 20:36:36 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2A112160ABC; Mon, 5 Sep 2016 18:36:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9633F160AB0 for ; Mon, 5 Sep 2016 20:36:35 +0200 (CEST) Received: (qmail 28444 invoked by uid 500); 5 Sep 2016 18:36:34 -0000 Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@shiro.apache.org Delivered-To: mailing list dev@shiro.apache.org Received: (qmail 28429 invoked by uid 99); 5 Sep 2016 18:36:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2016 18:36:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 154E9C7EAA for ; Mon, 5 Sep 2016 18:36:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id XNNyDt3fNMA2 for ; Mon, 5 Sep 2016 18:36:31 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id AD7755F1A0 for ; Mon, 5 Sep 2016 18:36:31 +0000 (UTC) Received: from mjim.nabble.com (unknown [162.253.133.84]) by mwork.nabble.com (Postfix) with ESMTP id 1D3D348A84870 for ; Mon, 5 Sep 2016 11:36:31 -0700 (MST) Date: Mon, 5 Sep 2016 11:36:31 -0700 (MST) From: "joao.tab" To: dev@shiro.apache.org Message-ID: <1473100591087-7579425.post@n2.nabble.com> Subject: Support for Hazelcast 3.x for OSGi setup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable archived-at: Mon, 05 Sep 2016 18:36:36 -0000 Hi, I've just upgraded to Shiro 1.3.1 and noticed it now has native Hazelcas= t support through shiro-hazelcast. It seems though that the OSGi bundle manifest limits Hazelcast to [2.4,3= ) Is there any particular limitation with Hazelcast 3.x? I've been using Shiro 1.2.5 with Hazelcast 3.6.2 with a fork from the Shiro 1.3 HazelcastCacheManager and everything seemed to work fine. Cheers, Jo=C3=A3o Taborda -- View this message in context: http://shiro-developer.582600.n2.nabble.com/S= upport-for-Hazelcast-3-x-for-OSGi-setup-tp7579425.html Sent from the Shiro Developer mailing list archive at Nabble.com.