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.

Fran├žois


On Tue, Feb 11, 2014 at 3:59 PM, ChambreNoire <a...@tentelemed.com> 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:
> http://apache-wicket.1842946.n4.nabble.com/Submitting-values-for-null-associations-tp4664365p4664371.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
>
>

Reply via email to