Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD30C102AE for ; Thu, 13 Feb 2014 18:33:27 +0000 (UTC) Received: (qmail 36988 invoked by uid 500); 13 Feb 2014 18:33:21 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 36880 invoked by uid 500); 13 Feb 2014 18:33:20 -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 36534 invoked by uid 99); 13 Feb 2014 18:33:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Feb 2014 18:33:19 +0000 Date: Thu, 13 Feb 2014 18:33:19 +0000 (UTC) From: "Aron Lurie (JIRA)" To: dev@openjpa.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OPENJPA-2022) Reversemappingtooltask with oracle is failing like in OPENJPA-1940 previous bug MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900578#comment-13900578 ] Aron Lurie commented on OPENJPA-2022: ------------------------------------- The attached patch also worked for me. Why hasn't it been applied to trunk? https://svn.apache.org/repos/asf/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/schema/SchemaGenerator.java > Reversemappingtooltask with oracle is failing like in OPENJPA-1940 previous bug > ------------------------------------------------------------------------------- > > Key: OPENJPA-2022 > URL: https://issues.apache.org/jira/browse/OPENJPA-2022 > Project: OpenJPA > Issue Type: Bug > Components: tooling > Affects Versions: 2.1.0, 2.1.1, 2.2.0 > Environment: Woking on a windows pc with a oracle 10g express database, eclipse helios, using oracle 11.2.0.2 driver. > Reporter: sebastien morissette > Assignee: Michael Dick > Fix For: 2.4.0 > > Attachments: OPENJPA-2022-trunk.patch > > > When running either of the versions of the reversemappingtool as reported in the 1940 bug as fixed, i get the same error as in 2.1.0 : > [reversemappingtool] 2363 openjpa INFO [main] openjpa.Tool - ReverseMappingTool : generating classes. > [reversemappingtool] 2365 openjpa INFO [main] openjpa.MetaData - Table "RMTOOLS."AppUsers"" could not be reverse mapped. This means that the table does not have a primary key (primary keys are required to establish unique identifiers for all persistent objects) and does not match a known pattern for a table used for cross-reference or value collections. > [reversemappingtool] 2366 openjpa INFO [main] openjpa.MetaData - Table "RMTOOLS."CredentialTypes"" could not be reverse mapped. This means that the table does not have a primary key (primary keys are required to establish unique identifiers for all persistent objects) and does not match a known pattern for a table used for cross-reference or value collections. > [reversemappingtool] 2366 openjpa INFO [main] openjpa.MetaData - Table "RMTOOLS."Credentials"" could not be reverse mapped. This means that the table does not have a primary key (primary keys are required to establish unique identifiers for all persistent objects) and does not match a known pattern for a table used for cross-reference or value collections. > this happens for all my tables. Is it possible this bug was reintroduced? > thanks -- This message was sent by Atlassian JIRA (v6.1.5#6160)