Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of awhite@bea.com designates
 66.248.192.39 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <7D856CDFE035FF45A0420ACBD71BDD6303D1F4EA@repbex02.amer.bea.com>
References: <7D856CDFE035FF45A0420ACBD71BDD6303D1F4EA@repbex02.amer.bea.com>
Content-Type: text/plain; charset=US-ASCII
Message-Id: <E6A8E235-EB96-48FB-A131-42C288D2F9A2@bea.com>
Content-Transfer-Encoding: 7bit
From: Abe White <awhite@bea.com>
Subject: Re: OPENJPA-182: reuse Connection constants or create our own?
Date: Fri, 6 Apr 2007 16:16:48 -0500
To: open-jpa-dev@incubator.apache.org


> I think that JDBCFetchPlan should take a Java 5 enum, and
> JDBCFetchConfiguration should use the Connection values.

Certainly JDBCFetchConfiguration should use the Connection values.  I  
personally have never had a problem with symbolic constants for  
settings, but enums for the FetchPlan are cool too.  So long as the  
JPA QueryImpl parses the enum value and its string form correctly  
when using it as a hint.

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.