Is it possibly some sort of classloading issue? I know in the past we've seen the 'The name "x" is not a recognized entity or identifier. Perhaps you meant n' in the past, but it seems like most of those were cleaned up.
One shot it the dark would be to try to enable <property name="openjpa. MetaDataRepository" value="Preload=true"/> to see if that helps. Thanks, Rick On Wed, Feb 12, 2014 at 12:52 PM, Sebarry <seanjamesba...@yahoo.co.uk>wrote: > Hi Rick, > > Here's the contents of my persistence.xml > > <persistence xmlns="http://java.sun.com/xml/ns/persistence"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > version="1.0"> > > <persistence-unit name="person2" transaction-type="JTA"> > > <jta-data-source>osgi:service/javax.sql.XADataSource/( > osgi.jndi.service.name=jdbc/derbydsxa)</jta-data-source> > <class>net.lr.tutorial.karaf.camel.jpa2jms.model.Person</class> > <exclude-unlisted-classes>true</exclude-unlisted-classes> > > <properties> > > <property name="openjpa.jdbc.SynchronizeMappings" > value="buildSchema"/> > <property name="openjpa.jdbc.DBDictionary" value="derby"/> > </properties> > </persistence-unit> > > </persistence> > > Regards, > > Sean > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/org-apache-openjpa-persistence-ArgumentException-An-error-occurred-while-parsing-the-query-filter-se-tp7585976p7585979.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > -- *Rick Curtis*
