Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 39445 invoked from network); 24 Feb 2010 21:35:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2010 21:35:48 -0000 Received: (qmail 92365 invoked by uid 500); 24 Feb 2010 21:35:48 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 92304 invoked by uid 500); 24 Feb 2010 21:35:48 -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 92294 invoked by uid 99); 24 Feb 2010 21:35:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2010 21:35:48 +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; Wed, 24 Feb 2010 21:35:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D663A234C045 for ; Wed, 24 Feb 2010 13:35:27 -0800 (PST) Message-ID: <1838108238.505261267047327862.JavaMail.jira@brutus.apache.org> Date: Wed, 24 Feb 2010 21:35:27 +0000 (UTC) From: "Ravi P Palacherla (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Created: (OPENJPA-1535) Inconsistency in exceptions thrown from MetaDataRepository.resolve() MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Inconsistency in exceptions thrown from MetaDataRepository.resolve() -------------------------------------------------------------------- Key: OPENJPA-1535 URL: https://issues.apache.org/jira/browse/OPENJPA-1535 Project: OpenJPA Issue Type: Bug Affects Versions: 2.0.0-beta, 1.1.0 Reporter: Ravi P Palacherla Assignee: Ravi P Palacherla There is an inconsistency in the way exceptions are thrown from MetaDataRepository.resolve(ClassMetaData). If there are more than one error encountered while resolving metadata then all these exceptions are wrapped inside MetaDataException and the MetaDataException is thrown. If there is only single exception thrown then that exception is thrown without wrapping inside MetaDataException. So, in case of single error encountered any exception ( need not be MetaDataException) is thrown but in case of multiple errors encountered MetaDataException is thrown. Now, there is a method loadRegisteredClassMetaData() inside same class which calls the above resolve method ( via other method calls). This loadRegisteredClassMetaData() catches MetaDataException and logs a warning, which is an expected behavior. But as resolve(), in case of a single error , throws an exception other than MetaDataException loadRegisteredClassMetaData() is not able to catch this Exception. I think this inconsistence behavior has to be fixed inside MetaDataRepository.resolve(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.