Hi Paul,
thanks for quick fix.
I have another one. Is it ok to report here or better create JIRA issue ?
My custom IdentityGenerator ( inherited from layer hierarchy ) is probably
overwritten with default one.
My guess is that ModuleAssemblyImpl.addDefaultAssemblers() is not respecting
hierarchy inheritance.
I have custom IdentityGenerator declared in BottomLayer but used in UpperLayer.
thanks,
- Tibor
> On May 21, 2017, at 5:45 PM, Paul Merlin <[email protected]> wrote:
>
> Hi Tibor,
>
> Le 2017-05-21 17:11, Tibor Mlynarik a écrit :
>> Hi ,
>> I am trying to port my 2.0 based application to latest 3.0 develop branch.
>> It seems that Association.set() is not allowing null.
>> ( quick look at AssociationInstance.set() shows possible NPE at line 67 )
>
> Thank you!
> Looks like this NPE was introduced during the Identity refactoring.
>
> I just pushed a fix to `develop` with some added coverage.
>
