Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of simone.tripodi@gmail.com
 designates 74.125.82.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=D6hdOlf9qqAmb+d6vBIfuzOS4Ga9MnUbHDSQJ36wtokfdZN7zVPL+XNgxGc2zQb1yt
         v8popPYNV9Z/MqX8x8+BvESUb6YU4r0iP+pqOE/B5drTtooQ2PSkiLvW5BjdRlS8bYnT
         UU/oTwwSO5TJZ1OXnTS4zEx37Cyx+gvhNfkyg=
MIME-Version: 1.0
Sender: simone.tripodi@gmail.com
In-Reply-To: <4DC30581.2030600@gmail.com>
References: <4DC2D9B7.30804@apache.org>
	<4DC2DDD2.6020206@apache.org>
	<4DC2F36A.40308@gmail.com>
	<BANLkTimdd7widAS=uc+W6Jv6bsUZ859rhw@mail.gmail.com>
	<4DC30581.2030600@gmail.com>
Date: Thu, 5 May 2011 22:39:14 +0200
Message-ID: <BANLkTimNz-mC0JA5RdfyYuR9XrQLZLCM4w@mail.gmail.com>
Subject: Re: [DBCP2][Proposal] Drop JOCL support
From: Simone Tripodi <simonetripodi@apache.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

YES you're absolutely right!!! :)
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/


On Thu, May 5, 2011 at 10:16 PM, Phil Steitz <phil.steitz@gmail.com> wrote:
> On 5/5/11 1:13 PM, Simone Tripodi wrote:
>> +1
>>
>> I wonder if any developer has the need to use JOCL today, given the
>> configuration super-power provided by modern IoC containers/DI
>> frameworks
> Or even Commons Digester which IIRC, this stuff preceded.
>
> Phil
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Thu, May 5, 2011 at 8:58 PM, Phil Steitz <phil.steitz@gmail.com> wrot=
e:
>>> On 5/5/11 10:26 AM, Emmanuel Bourg wrote:
>>>> Le 05/05/2011 19:09, Mark Thomas a =C3=A9crit :
>>>>> I couldn't find much evidence (via Google) of JOCL being in
>>>>> current or
>>>>> recent usage therefore I'd like to drop it from DBCP 2.0.0 onwards.
>>>>>
>>>>> Any objections?
>>>> Never heard of JOCL, is this the xml serialization format that was
>>>> introduced in Java 1.4 (with java.beans.XMLEncoder/Decoder) ?
>>>>
>>>> I don't think DBCP should be tied to a serialization format, so +1
>>>> for removing this part in DBCP 2.
>>> It is really a configuration specification language. =C2=A0See
>>> *http://s.apache.org/vT.
>>>
>>> Phil
>>> *
>>>> Emmanuel Bourg
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org