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 ABA05CE2E for ; Fri, 13 Jul 2012 09:26:37 +0000 (UTC) Received: (qmail 13421 invoked by uid 500); 13 Jul 2012 09:26:37 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 13261 invoked by uid 500); 13 Jul 2012 09:26: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 13217 invoked by uid 99); 13 Jul 2012 09:26:34 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2012 09:26:34 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 5C78D141887 for ; Fri, 13 Jul 2012 09:26:34 +0000 (UTC) Date: Fri, 13 Jul 2012 09:26:33 +0000 (UTC) From: "Mark Struberg (JIRA)" To: dev@openjpa.apache.org Message-ID: <1062972664.47324.1342171594382.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1585299288.41890.1342102835135.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (OPENJPA-2229) Persistence entities not recognized when deploying on JBoss AS 7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OPENJPA-2229?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13= 413602#comment-13413602 ]=20 Mark Struberg commented on OPENJPA-2229: ---------------------------------------- perfectly fine. I just wanted to raise the awareness that this might hit us= in other situations as well. Not only with other url prefixes, but also in= other locations in the OpenJPA codebase. It would be perfect if we can mov= e this to a common helper class somehow. =20 > Persistence entities not recognized when deploying on JBoss AS 7.1 > ------------------------------------------------------------------ > > Key: OPENJPA-2229 > URL: https://issues.apache.org/jira/browse/OPENJPA-2229 > Project: OpenJPA > Issue Type: Bug > Components: kernel > Affects Versions: 2.2.0, 2.3.0, 2.2.1 > Environment: JBoss AS 7.1.1-Final > Reporter: Francesco Chicchiricc=C3=B2 > Attachments: jboss-vfs.patch > > > I've found this guide [1] about using OenJPA 2.2.0 and JBoss 7.1: I had s= ome minor issues (already reported on that page) easily solved, but then I = came to this exception, thrown at every JPA query: > org.apache.openjpa.pe= rsistence.ArgumentException: An error occurred while parsing the query filt= er "SELECT e FROM ExternalResource e". Error message: The name "ExternalRe= source" is not a recognized entity or identifier. Perhaps you meant Externa= lResource, which is a close match. Known entity names: [ExternalResource, A= bstractSchema, RAttrUniqueValue, AbstractVirAttr, Membership, TaskExec, Syn= copeConf, Report, RAttr, AbstractExec, SyncopeLogger, USchema, MAttr, Passw= ordPolicy, RSchema, MSchema, MAttrValue, MAttrUniqueValue, AbstractAttr, Ab= stractDerSchema, AbstractVirSchema, UAttr, AccountPolicy, RAttrValue, UAttr= Value, ReportExec, SyncopeUser, Notification, ConnInstance, AbstractDerAttr= , AbstractAttrValue, SyncopeRole, SyncPolicy, Policy, ReportletConfInstance= , Task, UAttrUniqueValue, Entitlement, SchemaMapping, UserRequest] > at org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parse= Exception(AbstractExpressionBuilder.java:119) [openjpa-kernel-2.2.0.jar:2.2= .0] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getClassM= etaData(JPQLExpressionBuilder.java:194) [openjpa-kernel-2.2.0.jar:2.2.0] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.resolveCl= assMetaData(JPQLExpressionBuilder.java:167) [openjpa-kernel-2.2.0.jar:2.2.0= ] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandid= ateMetaData(JPQLExpressionBuilder.java:242) [openjpa-kernel-2.2.0.jar:2.2.0= ] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandid= ateMetaData(JPQLExpressionBuilder.java:212) [openjpa-kernel-2.2.0.jar:2.2.0= ] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandid= ateType(JPQLExpressionBuilder.java:205) [openjpa-kernel-2.2.0.jar:2.2.0] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.access$20= 0(JPQLExpressionBuilder.java:80) [openjpa-kernel-2.2.0.jar:2.2.0] > at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQ= L.populate(JPQLExpressionBuilder.java:2417) [openjpa-kernel-2.2.0.jar:2.2.0= ] > at org.apache.openjpa.kernel.jpql.JPQLParser.populate(JPQLParser.= java:61) [openjpa-kernel-2.2.0.jar:2.2.0] > After some deeper investigation, I've found that the problem resides in t= he vfs: JBoss URLs, currently not managed. > [1] https://community.jboss.org/thread/201329=20 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira