Tatu Saloranta

Ahhh. Reading exception more carefully, realized the problem is with type being used taken as `String[]` (from `String ...` for Creator property) while calling (correctly) Setter method (which takes `Collection`)....

Yes, sounds like a bug. Thank you for thorough investigation and notes. I haven't had to look into this one but hope to address it.

@wheredevel I have not had time to look further, but sounds like legit bug.

Alas test uses Lombok. This is problematic as I do not have (nor plan to) install Lombok, as it does not (unlike most other libraries) work using just basic build...

... that aside I do appreciate reproductions, which are greatly appreciated! :-D

Unfortunately I am unable to reproduce the issue at this point. When simplifying this to just use fields, default constructor, problem does not occur. I assume it would be reproducible...

@wheredevel I know it is possible, but I do not want to install jars for arbitrary frameworks in my classpath. This is why from this point on no Lombok dependencies...

@atribe Thank you for digging this up. Just one follow-up question: do you know what `@AllArgsConstructor` would mean in terms of constructor added? I am not sure if Lombok could...

@shongywong If you are also using Lombok, you probably will need to avoid `@ AllArgsConstructor`. If not, it is necessary to avoid adding `@JsonBackReference` annotated parameter in `@JsonCreator` annotated (or,...

@atribe Thank you! Without having tested this, I think the problem really isn't Lombok, but combination of just two things: 1. Constructor as creator (not a problem in itself) 2....