As Hibernate save a new Job instance when you save the User if the relation is empty why don't you load the job (with an eager fetching strategy) when you load the user ?
François On Tue, Feb 11, 2014 at 3:22 PM, ChambreNoire <a...@tentelemed.com> wrote: > I forgot to mention, the reason I don't systematically make a new Job > instance is that when saving the form hibernate creates a new Job instance > which is effectively empty if no Job details have been input. > > Chambre > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Submitting-values-for-null-associations-tp4664365p4664369.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
