Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of elakito@gmail.com designates
 209.85.220.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACBZuv7-4B7hS2TM1_NRbxUDDJg_UppZrYCfX7GJV_zb+0N7xg@mail.gmail.com>
References: 
 <CAF8t5Xv2y3duZygdp+Y8g+8iOZMmoHcpO2UHwtVBNyiHoV0TNw@mail.gmail.com>
	<FA02514C-D8C9-4119-8A75-1C05FFB8E143@apache.org>
	<CACBZuv7-4B7hS2TM1_NRbxUDDJg_UppZrYCfX7GJV_zb+0N7xg@mail.gmail.com>
Date: Thu, 4 Jul 2013 15:23:19 +0200
Message-ID: 
 <CAF8t5XsarQVTdYzOZYghxUbcv_wYyDUH38SDp6JAZJJW=mg9VA@mail.gmail.com>
Subject: Re: ehcache version used in cxf build
From: Aki Yoshida <elakito@gmail.com>
To: Jason Pell <jason@pellcorp.com>
Cc: dev@cxf.apache.org
Content-Type: multipart/alternative; boundary=047d7bacc7b04cea9d04e0af7bd2

--047d7bacc7b04cea9d04e0af7bd2
Content-Type: text/plain; charset=ISO-8859-1

hi,
thanks all for the information.

Is this issue about the manager instance that is created using the create
method in the newer version (eg., 2.5.2 and also 2.6.6, etc) being a
singleton? In other words, in the newer version to have the same behavior,
the newly introduced method newInstance needs to be instead called?

If that's the case, we should put the code to handle both cases in all code
lines.

thanks.
aki


2013/7/4 Jason Pell <jason@pellcorp.com>

> Sorry guys i never got back to this one. Would be easier i should think to
> fix this for 3.0 and no longer support the old version at all thus no
> reflection magic.
> On Jul 4, 2013 7:04 AM, "Daniel Kulp" <dkulp@apache.org> wrote:
>
>> Aki,
>>
>> This was on my todo list to look at, just never have managed to find the
>> time.   There is an issue logged about it:
>>
>> https://issues.apache.org/jira/browse/CXF-4577
>>
>> If you have time, feel free to grab it and see what you can find out.
>>
>> Dan
>>
>>
>>
>>
>> On Jul 3, 2013, at 4:58 PM, Aki Yoshida <elakito@gmail.com> wrote:
>>
>> > cxf's trunk and branches (2.7.x, 2.6.x, etc) all use ehcache 2.5.1 and
>> > create the karaf feature with the corresponding smx's bundle version.
>> But
>> > the version range specified in the package imports is set as
>> [2.5.0,3.0.0),
>> > so we could use a newer version in runtime.
>> >
>> > As ehcache 2.5.1 is rather old (from 2012-01) and there are newer
>> versions
>> > such as 2.6.6 (2013-05) and 2.7.2 (2013-07) which is already an
>> > osgi-bundle,  I was wondering if we can use a newer version for trunk's
>> > build. There are some disappeared classes and other changes, but the
>> usage
>> > in cxf seem to be compatible with these versions. I tried both 2.6.6 and
>> > 2.7.2, and the build itself seems to run without problems.
>> >
>> > How do you think about upgrading ehcache to ehcache 2.7.2 for trunk so
>> that
>> > we can test cxf not just against old ehcache 2.5.1?
>> >
>> > As comparison, camel trunk uses ehcache 2.7.0, while 2.11.x uses 2.5.2.
>> >
>> > regards, aki
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>

--047d7bacc7b04cea9d04e0af7bd2--