Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 94032 invoked from network); 12 Jan 2010 16:46:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jan 2010 16:46:17 -0000 Received: (qmail 58585 invoked by uid 500); 12 Jan 2010 16:46:17 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 58575 invoked by uid 99); 12 Jan 2010 16:46:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jan 2010 16:46:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jan 2010 16:46:15 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 841F7234C48D for ; Tue, 12 Jan 2010 08:45:54 -0800 (PST) Message-ID: <1879311646.184151263314754540.JavaMail.jira@brutus.apache.org> Date: Tue, 12 Jan 2010 16:45:54 +0000 (UTC) From: "Andy Jefferson (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Commented: (JDO-630) Support specification of exact class in SingleFieldIdentity In-Reply-To: <610370216.1239780135294.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JDO-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799264#action_12799264 ] Andy Jefferson commented on JDO-630: ------------------------------------ Re: The NPE is here Errm, no, you misunderstand :-). I want to **see** the NPE and its stack trace ... which is presumably in DN code. Without that I would have to run the test that isn't present in SVN > Support specification of exact class in SingleFieldIdentity > ----------------------------------------------------------- > > Key: JDO-630 > URL: https://issues.apache.org/jira/browse/JDO-630 > Project: JDO > Issue Type: Improvement > Components: specification, tck2 > Reporter: Andy Jefferson > Assignee: Craig Russell > Fix For: JDO 2 maintenance release 3 > > Attachments: jdo-630.patch > > > When calling PersistenceManager.getObjectById() with a SingleFieldIdentity, there seems to be no way of avoiding the following > (if the implementation decides to do so): > "It is an implementation decision whether to access the data store, if required to determine the exact class. This will be the case of inheritance, where multiple PersistenceCapable classes share the same ObjectId class." > Now when I know for sure that the targetClassName of the given SingleFieldIdentity already denotes the correct class for the given id, how can I avoid that additional roundtrip to the database for finding the exact class? > It would be useful to have a way of specifying a SingleFieldIdentity to be for the exact class specified. This could be done by addition of methods > void setExact(boolean flag); > boolean getExact(); > to SingleFieldIdentity -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.