I'm trying to setup a one to one relationship in the following manner.

public Class OneToOneRoot() {

@Id
@GeneratedValue(strategy=GenerationType.AUTO)
private long id;

private String name;

@OneToOne(fetch = FetchType.LAZY, mappedBy = "root", cascade = CascadeType.ALL)
private OneSharedId sharedId;

}

public Class OneSharedId() {

@GenericGenerator(name = "generator", strategy = "foreign",
parameters = @Parameter(name = "property", value = "root"))
@Id
@GeneratedValue(generator = "generator")
private long id;

private String name;

@OneToOne(fetch = FetchType.LAZY)
@PrimaryKeyJoinColumn
private OneToOneRoot root;

}

Basically, the two classes share the same id key. Create, Update and Delete operations seem to function without issue. However, I get some weird error results for a simple criteria query.

Criteria query = session.createCriteria(OneToOneRoot.class);
OneSharedId shared = new OneSharedId();
shared.setId(2);
query.add(Restrictions.eq("sharedId",shared));
List<OneToOneRoot> matches = query.list();

I have tried many variations, with the same error results:

Exception in thread "main" org.hibernate.exception.SQLGrammarException: could not extract ResultSet
Caused by: java.sql.SQLException: No value specified for parameter 1
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1078)

I understand that using the "shareId" object as the query seems silly, considering the id is shared, but we have some existing, "too smart for its own good" code, that auto generates criteria in this manner based on meta data. Is my mapping incorrect? Is the assumption that this criteria should work flawed?

I would do something like this: