Error when using CDATA in orm.xml

[Edwin Dalorzo]

Hi everyone!

I am using TopLink Essentials implementation of JPA. I created a small client application running with JSE 1.5.15.

I declared the following named query in my orm.xml file:

</named-query>
 <named-query name="findLatestExchangeRate">
  SELECT a
  FROM ExchangeRate a
  WHERE
  a.code = :currency AND 
  a.date = (SELECT MAX(b.date) 
  FROM ExchangeRate b 
  WHERE b.code = :currency AND b.date &lt;= :before)
 </query>
</named-query>

I tested this and it worked like a charm.

Then, I decided that, in order to avoid the use of XML entities, I could place the query in a CDATA section. Somehwhat like this:

<named-query name="findLatestExchangeRate">
 <query>
  <![CDATA[
   SELECT a
   FROM ExchangeRate a
   WHERE
   a.code = :currency AND 
   a.date = (SELECT MAX(b.date) 
   FROM ExchangeRate b 
   WHERE b.code = :currency AND b.date <= :before)
  ]]>
  </query>
</named-query>

Then I got an error when I try to run the program. The persistence context does not even gets created. It fails when I try to crete the EntityManagerFactory.

This is really weird:

Exception in thread "main" Local Exception Stack: 
Exception [TOPLINK-8028] (Oracle TopLink Essentials - 2.0.1 (Build SNAPSHOT (02/01/2008))): oracle.toplink.essentials.exceptions.EJBQLException
Exception Description: Syntax error parsing the query [findLatestExchangeRate: 

], line 1, column 41: unexpected end of query.
Internal Exception: line 1:41: unexpected token: null
at oracle.toplink.essentials.exceptions.EJBQLException.unexpectedEOF(EJBQLException.java:419)
at oracle.toplink.essentials.internal.parsing.ejbql.EJBQLParser.handleANTLRException(EJBQLParser.java:346)
at oracle.toplink.essentials.internal.parsing.ejbql.EJBQLParser.addError(EJBQLParser.java:278)
at oracle.toplink.essentials.internal.parsing.ejbql.EJBQLParser.reportError(EJBQLParser.java:378)
at oracle.toplink.essentials.internal.parsing.ejbql.antlr273.EJBQLParser.document(EJBQLParser.java:156)
at oracle.toplink.essentials.internal.parsing.ejbql.EJBQLParser.parse(EJBQLParser.java:166)
at oracle.toplink.essentials.internal.parsing.ejbql.EJBQLParser.buildParseTree(EJBQLParser.java:127)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.buildEJBQLDatabaseQuery(EJBQueryImpl.java:215)
at oracle.toplink.essentials.queryframework.EJBQLPlaceHolderQuery.processEjbQLQuery(EJBQLPlaceHolderQuery.java:111)
at oracle.toplink.essentials.internal.sessions.AbstractSession.processEJBQLQueries(AbstractSession.java:2059)
at oracle.toplink.essentials.internal.sessions.AbstractSession.processEJBQLQueries(AbstractSession.java:2046)
at oracle.toplink.essentials.internal.sessions.DatabaseSessionImpl.postConnectDatasource(DatabaseSessionImpl.java:724)
at oracle.toplink.essentials.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:604)
at oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:280)
at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:229)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:93)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:126)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:120)
at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:91)
at Main.main(Main.java:22)
Caused by: line 1:41: unexpected token: null
at oracle.toplink.essentials.internal.parsing.ejbql.antlr273.EJBQLParser.document(EJBQLParser.java:150)
... 15 more

Any idea about what is going on here?

Thanks in advance,
Edwin Dalorzo
[ October 13, 2008: Message edited by: Edwin Dalorzo ]

[Juhani Lehtimaki]

I have the exactly same problem. The orm.xml file works just fine with OpenJPA but TopLink is unable to handle it. Is there a way to fix this? I don't want to use XML entities in the queries.

[Edwin Dalorzo]

So far I solved the problem using EclipseLink instead of TopLink Essentials. That's all I could recommend to be done by now.