openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <>
Subject [jira] [Commented] (OPENJPA-2229) Persistence entities not recognized when deploying on JBoss AS 7.1
Date Thu, 12 Jul 2012 15:14:35 GMT


Francesco Chicchiriccò commented on OPENJPA-2229:

Hi Rick,
this sounds very nice!

Once you'll apply the patch and commit, will the updated Maven artifacts be published immediately?
I'd love to be able to have it with 2.2.1-SNAPSHOT ;-)

> Persistence entities not recognized when deploying on JBoss AS 7.1
> ------------------------------------------------------------------
>                 Key: OPENJPA-2229
>                 URL:
>             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ò
>         Attachments: jboss-vfs.patch
> I've found this guide [1] about using OenJPA 2.2.0 and JBoss 7.1: I had some minor issues
(already reported on that page) easily solved, but then I came to this exception, thrown at
every JPA query:
> <openjpa-2.2.0-r422266:1244990 nonfatal user error> org.apache.openjpa.persistence.ArgumentException:
An error occurred while parsing the query filter "SELECT e FROM  ExternalResource e". Error
message: The name "ExternalResource" is not a recognized entity or identifier. Perhaps you
meant ExternalResource, which is a close match. Known entity names: [ExternalResource, AbstractSchema,
RAttrUniqueValue, AbstractVirAttr, Membership, TaskExec, SyncopeConf, Report, RAttr, AbstractExec,
SyncopeLogger, USchema, MAttr, PasswordPolicy, RSchema, MSchema, MAttrValue, MAttrUniqueValue,
AbstractAttr, AbstractDerSchema, AbstractVirSchema, UAttr, AccountPolicy, RAttrValue, UAttrValue,
ReportExec, SyncopeUser, Notification, ConnInstance, AbstractDerAttr, AbstractAttrValue, SyncopeRole,
SyncPolicy, Policy, ReportletConfInstance, Task, UAttrUniqueValue, Entitlement, SchemaMapping,
>         at org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getClassMetaData(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.resolveClassMetaData(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateMetaData(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getCandidateType(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.access$200(
>         at org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.populate(
>         at org.apache.openjpa.kernel.jpql.JPQLParser.populate( [openjpa-kernel-2.2.0.jar:2.2.0]
> After some deeper investigation, I've found that the problem resides in the vfs: JBoss
URLs, currently not managed.
> [1] 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message