From dev-return-12084-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Tue May 26 14:48:58 2009 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 89316 invoked from network); 26 May 2009 14:48:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 May 2009 14:48:58 -0000 Received: (qmail 38703 invoked by uid 500); 26 May 2009 14:42:31 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 38135 invoked by uid 500); 26 May 2009 14:42:29 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 38099 invoked by uid 99); 26 May 2009 14:42:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2009 14:42:29 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-fx0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2009 14:42:21 +0000 Received: by fxm22 with SMTP id 22so3884027fxm.9 for ; Tue, 26 May 2009 07:41:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=rmezrezimGohiKG5V61IBE5olvaQgTt1Gmwuw5pTXzY=; b=xknvEo4CedJZB9X/294B5IH6HTP0I4xNzjSejAz4we8wFS6rvkCz6U5rozK8Ho2Dhk iY5DO0yr3hY2Yia1Fz/CvPt+NvfErLkcrgXs5bG5q7vh1qM+JQiO0CxN+tRTvZG6wu8n UvfOoN6UYI4ivwT9E0P+tMyzBcc13OBESYOYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=oY1kQoSwg6TaAbzGejS0Pu5hcyrp/iD5MOqCBH6hFbx2M5Zkz11yMZUd+X1YtwRP9s FEyO/JOGZDtTk1hF9zg7TAeIfD5BlaIu8cMsabjxrEIlrAjeOqE9B9SweaD2rKmdmKH3 KLpKXdHo/9U4krddZL3C9hcJDOt+9lJpV2XXQ= MIME-Version: 1.0 Received: by 10.223.122.15 with SMTP id j15mr4476712far.74.1243348919136; Tue, 26 May 2009 07:41:59 -0700 (PDT) In-Reply-To: <5256f0fb.4f145d36.4a196a51.c4713@o2.pl> References: <5256f0fb.4f145d36.4a196a51.c4713@o2.pl> Date: Tue, 26 May 2009 09:41:59 -0500 Message-ID: <72c1350f0905260741p4c4efdcbu2dff8c5f987e79a3@mail.gmail.com> Subject: Re: JDBC 3 reflection in DBDictionary From: Michael Dick To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=001636c5a723a832ec046ad1ba0a X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a723a832ec046ad1ba0a Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable +1 On Sun, May 24, 2009 at 10:40 AM, Mi=B3osz Tylenda wrote: > Hi All! > > A couple of LOB related methods in DBDictionary use reflection to invoke > JDBC 3 methods. Since we now require JDBC >=3D 3 during compilation, I th= ought > of replacing their bodies with plain metohd calls instead of reflected on= es. > This will slightly reduce the size of that big class and make stack trace= s > easier to read. Has someone an opinion? > > The methods are: > putBytes, > putString, > putChars, > invokePutLobMethod. > > Regards, > Milosz > > --001636c5a723a832ec046ad1ba0a--