Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of ljnelson@gmail.com designates
 209.85.160.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=r+9n6F2qhaEWuB/CjGB9FNFGtHQxgKXEocjVaV0jd9fvJvGuP5MJ9Xj5nURSP0W/jD
         e3SgGKEItCe2mW7NHJPL5Zm4iQzHSopKWJ/uBMN4ippSv1VSBg0CPQUkwEqjOnt6dEz5
         a+106iXsmmEzq906kJ9PZVoN7S+LzJvxsrNjE=
MIME-Version: 1.0
Date: Wed, 24 Feb 2010 15:18:11 -0500
Message-ID: <2c0ebf0c1002241218m35e57d4do5889caacc4c88930@mail.gmail.com>
Subject: clone() contract broken for JDBCConfigurationImpl instances
From: Laird Nelson <ljnelson@gmail.com>
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=000e0cd61e6483c1ec04805e5d18

--000e0cd61e6483c1ec04805e5d18
Content-Type: text/plain; charset=ISO-8859-1

Hello; JDBCConfigurationImpl, when cloned, drops its passwords on the floor.

This did not happen in version 1.2.2.

The problem is related to the introduction of the EncryptionProvider in the
2.0 line (and others).

The bug is here: https://issues.apache.org/jira/browse/OPENJPA-1534

This is a showstopper for me, but I'm not clear what the proper resolution
is (other than to implement clone() by calling super.clone() as should be
the case).

Thanks,
Laird

--000e0cd61e6483c1ec04805e5d18--