Hey there,
I m trying to use a named query from an optional mapping file that declares the entities mappings and is referenced in a persistence.xml file. Everything works fine when I use annotations.

However, when using a mapping file, named queries get warped.
The entities are mapped fine. So are the collections. Everything reads fine during deployment. However, a simple 'select e from example e' named query, throws an exception when executed. It turns out that the key column of a collection is included in the query! e.g. 'select e0.EXAMPLE_ID as e0_1, e0.EXAMPLE_DATE as e0_2, e0.EXAMPLE_1 as e0_3, e0.OTHER_ID as e0_4 from EXAMPLE e0'.

This is the mapped entity:

And the corresponding "other" entity mapping:


When used with annotations (strict EJB ones, no native Hibernate) everything works fine. Ideas anyone? Do note that it is imperative that I use xml mappings instead of annotations, as I want to enable hibernate's second level cache in a separate persistence unit declared in persistence.xml. Not all entities are declared in the xml file, but the ones that are, are fully defined.

Andreas

I have spent a lot of time trying to solve this. It has to do with the way composite id's get mapped. I have RTFM more than enough times. So I 'm going to post the 3 tables I want to get mapped and if anyone cares to help by drawing up the corresponding hibernate xml mappings (ejb annotations work fine), please do. Hibernate is version 3.2.6GA, Hibernate entity manager is 3.3.2GA and AS is GlassFish V2U2.

Table 1
Name table_1
Column name t1_a, type Integer, Primary Key
Column name t1_b, type String


Table 2
Name table_2
Column name t2_a, type Integer, Primary Key, Foreign Key referencing t1_a
Column name t2_b, type Date, Primary Key
Column name t2_c, type String
Column name t2_d, type String, Foreign Key referencing t3_a

Table 3
Name table_3
Column name t3_a, type String, Primary Key

Entity classes are table1, table2 plus table2PK and table3

Table 1 should have a one to many collection of Table 2
Table 3 should have a one to many collection of Table 2 too
Table 2 therefore must have a field for the composite (embedded) key, a field for column t2_c and another one for column t2_d plus the opposite end (many to one) for the collections.

The ejb-annotated (working) entity for table 2 looks like this:



I 'm going to get a beer now and watch Lost.


Cheers,
Andreas