Using 3.1.3.

I have an old DB with some composite keys (yay! fun mappings!) and my first POJO has a composite-id in a class of its own with the keys as below.

After running tests and inspecting the SQL output, it seems doing a findByExample ignores the values in the composite-id. Is there a method to tell Hibernate to incorporate the composite-id key values in the findByExample search?

As you can see, I'm using an interface for the entity POJO.

//composite primary key class
public class CardHolderId implements java.io.Serializable
{
private String paNumber;
private Short sequenceNumber;
etc......

//entity itself
public class BasicCardHolder implements java.io.Serializable, CardHolder
{
private CardHolderId id;
private String title;
private String firstName;
private String lastName;


Mapping:

No. From the ref docs, section 15.6, "Example queries":
Version properties, identifiers and associations are ignored. By default, null valued properties are excluded.

You could map the relvant columns twice: perhaps like this:The two new properties are read only (because they use formula="" instead of column=""), but can still be used to query by example.

Ok, thanks, I overlooked that statement in the docs, probably because I was concentrating on getting a one-to-many association to work with Example Query.

Your double mapping solution looks good initially but I think with the extra setters and getters on the persistent object, it will add more complexity than the current slightly verbose Criteria setup I have in the DAO.

In fact in this situation I think what I am going to do is just ditch Example Query and pass in the parameters seperately.