You use cascade="all" on the job relation.
When job is created, it should have at least one non-empty property.
Job's instance is null because it doesn't have any non empty property.


On Tue, Feb 11, 2014 at 3:59 PM, ChambreNoire <> wrote:

> Why would that make any difference? A null Job is still a null Job. Unless
> I'm missing something...
> --
> View this message in context:
> Sent from the Users forum mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Reply via email to