NamedQuery: IllegalArgumentException (Query not found) after externalizing entities

jpa ejb named-query
Hank picture Hank · May 29, 2011 · Viewed 21.8k times · Source

I have successfully used javax.persistence.NamedQuery in combination with JPA2. The named queries are defined at the top of the entity class files, and are used from Stateless EJBs (entity facade).

Now I had to extract the entity class files into a separate Jar file (so we can use them from a Google Web Toolkit project). Obviously I still incude the jar, but now the facade bean does not find the query anymore:

java.lang.IllegalArgumentException: NamedQuery of name: Store.findByExternalId not found.
    at org.eclipse.persistence.internal.jpa.EJBQueryImpl.getDatabaseQueryInternal(EJBQueryImpl.java:576)
    at org.eclipse.persistence.internal.jpa.EntityManagerImpl.createNamedQuery(EntityManagerImpl.java:1004)
    at com.sun.enterprise.container.common.impl.EntityManagerWrapper.createNamedQuery(EntityManagerWrapper.java:533)
    at com.skalio.bonusapp.server.StoreFacade.getByExternalId(StoreFacade.java:43)
    ...

What is the problem here? Can I not define NamedQueries in an external Jar?

I just found this link, suggesting to put the NamedQueries in XML files, not as annotations in the entity files. This could be an idea to solve my problem, but doesn't answer my question... ;)

Answer

Hank picture Hank · May 30, 2011

The solution is to specify the classes containing JPA Entities in the persistence.xml file:

<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
    <persistence-unit name="bonusAppServerPU" transaction-type="JTA">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/someDB</jta-data-source>
        <class>com.skalio.bonusapp.core.Store</class>
    </persistence-unit>
</persistence>

Background is that JPA needs to be told where to scan for annotations. The other option is to use the <jar-file></jar-file> node.

Related questions

What to put into jta-data-source of persistence.xml?

What value should I place into <jta-data-source> of my persistence.xml? In glassfish admin panel I created a datasource name "abcDS". In my jndi.properties (inside src/test/resources) I defined it like this: [...] abcDS=new://Resource?type=…

Read More
No entity found for query Exception

I am executing the following lines: String queString = "some query string" Query q1 = em.createNativeQuery(queString, T03CallsLog.class); T03CallsLog newCall; newCall = (T03CallsLog) q1.getSingleResult(); //this line cause the exception after the first time weird situation. if I …

Read More
Multiple writable mappings exception in EclipseLink

I have these tables: Which my intention is : A user can be a company or a person but each one of them have something in common, as username which is the email and password, so I used the JPA Tools …

Read More