Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 37038 invoked from network); 28 Apr 2008 13:16:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Apr 2008 13:16:33 -0000 Received: (qmail 10135 invoked by uid 500); 28 Apr 2008 13:16:35 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 9979 invoked by uid 500); 28 Apr 2008 13:16:35 -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 9961 invoked by uid 99); 28 Apr 2008 13:16:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Apr 2008 06:16:34 -0700 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; Mon, 28 Apr 2008 13:15:58 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CA14C234C115 for ; Mon, 28 Apr 2008 06:12:55 -0700 (PDT) Message-ID: <1430334227.1209388375813.JavaMail.jira@brutus> Date: Mon, 28 Apr 2008 06:12:55 -0700 (PDT) From: "Kevin Sutter (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Commented: (OPENJPA-513) More issues with the IBM JDK In-Reply-To: <33354365.1202588948519.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592803#action_12592803 ] Kevin Sutter commented on OPENJPA-513: -------------------------------------- Patrick, The problem is still "unresolved". From an IBM JDK environment viewpoint, the problem still exists. From a Sun JDK viewpoint, the problem would still exist if we didn't have that special code in the XMLMetaDataParser initializer which bypasses validation. So, as my previous remarks indicated, we are running without validation for the Sun JDK and with validation for all other JDKs. If that Xerces parser problem would ever get resolved in the Sun JDK, then we'd be hitting the same problem with the Sun JDK. The testcase in question has been "disabled" since mid-Feb 2008. Technically, it's still an open Issue. Kevin > More issues with the IBM JDK > ---------------------------- > > Key: OPENJPA-513 > URL: https://issues.apache.org/jira/browse/OPENJPA-513 > Project: OpenJPA > Issue Type: Sub-task > Components: build / infrastructure > Affects Versions: 1.0.2, 1.1.0 > Reporter: Kevin Sutter > Assignee: Kevin Sutter > Fix For: 1.1.0 > > > Now that I have a resolution (JDK patch) for OPENJPA-429, when I run a 1.1.0 build, I am getting some errors from the test phase of openjpa-persistence-jdbc. The following tests are failing according to the surefire report: > Results : > Tests in error: > testEntityListeners(org.apache.openjpa.persistence.callbacks.TestEntityListeners) > testGlobalListeners(org.apache.openjpa.persistence.callbacks.TestEntityListeners) > testPersistenceUnitWithoutXSD(org.apache.openjpa.persistence.xml.TestPersistenceUnitWithoutXSD) > testEnhancementOfAllPUsWithinAResource(org.apache.openjpa.enhance.TestEnhancementWithMultiplePUs) > Tests run: 568, Failures: 0, Errors: 4, Skipped: 0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.