posted 11 years ago
OK well this is not a Spring issue it is an ORM issue. You would probably get better attention posting this question in the ORM forum..
That said you have not posted enough information to really help you, but I am not sure you need a join table for this. You have a One to many so on the inverse side you will have a many to one. Since I have no idea the context of the application I will give you a different example. Consider an Employee and a Department, where a department has many employees but an employee can only belong to one department. Note the generation strategy was chosen for simplicity it is not usually the best choice.
The ddl for something like this could be like below (shown for Derby)