'Parent' DB Table references 'child' table twice

Question

I'm having fun learning a million new things at once, and I ran into a bit of a wall. I have made the following work using secondary backing beans, but I'm wondering if there isn't a nice simple connection of some sort that would let me avoid the extra code in the future.
So I have a few tables. We will say, table 'employee', 'address' and 'contact_info'.
Employee = {Integer ID,
  String name,
  Integer home_contact_id,
  Integer work_contact_id}
Contact_Info = {Integer ID, Integer address_id, String phone etc}
Address = {Integer ID, String Street, etc}
In the java code, is there a nice fast way to connect the getters of home_contact_id and work_contact_id to Contact_Info objects?
E.g. instead of
public Integer getHome_contact_id(){
return x;
// Something like this
@whichBloodyAnnotation
public WorkContactEntity getWork_contact_id(){
return y;
}I've already figured out the case for the link between the contact_info table and the address table, which is very nice.
Obviously the real world case is different; I would rather live with the extra code in Java than rebuild the data-structure.... On the other hand, if this is considered bad design, I suppose I'd like to know so, and why. I'm not a DB guy, as you may have guessed :~)
Thanks for any help!

Answer 1

I found the solution. Of course, it was incredibly simple.
For those looking, my assumption was that even uni-directional joins required the @annotatoin on both classes (since all the examples show this).
For the code below, you would just do the following:
@OneToOne
@JoinColumn(name = "col_name_in_Address") // 'id' in this case
public Address getHome_contact_id(){return x};
@OneToOne
@JoinColumn(name = "col_name_in_Address") // 'id' in this case
public Address getWork_contact_id(){return y};
No extra code (e.g. annotation) is required in the Address class, beyond that which specifies the columns etc.