fix for issue #48

[jwijgerd]

fix for issue #48

I am now either using the JsonSerializer that is passed in as a constructor property, if that is null the the BeanPropertyWriter.getSerializer() is used. This fixed the issue. I also added a testcase

[cowtowncoder]

Makes sense, thanks you for reporting this and contributing the fix!

One formality we have to do is to get a CLA (unless we already have one -- apologies if I have asked for this before):

https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf

and once provided I'll merge the fix, and CLA is good for any and all contributions for Jackson projects.

If you could print, fill, scan and email CLA to info at fasterxml dot com, that would be great. I can then merge the fix and it gets included in 2.5.1 release (plus I can backport it in 2.4 too assuming that's affected).

[jwijgerd]

Hi Tatu,

Thanx, will check and sign it tomorrow. 2.4 is affected as well (in fact I
found it in 2.4.4 and fixed it there first). Would be much appreciated if
it could be included in 2.4.5

Thanx,

Joost
Op 6 jan. 2015 19:45 schreef "Tatu Saloranta" [email protected]:

Makes sense, thanks you for reporting this and contributing the fix!

One formality we have to do is to get a CLA (unless we already have one --
apologies if I have asked for this before):

https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf

and once provided I'll merge the fix, and CLA is good for any and all
contributions for Jackson projects.

If you could print, fill, scan and email CLA to info at fasterxml dot
com, that would be great. I can then merge the fix and it gets included in
2.5.1 release (plus I can backport it in 2.4 too assuming that's affected).

—
Reply to this email directly or view it on GitHub
#49 (comment)
.

[cowtowncoder]

Yup, I will backport it; we are getting enough bugs to soon qualify for 2.4.5 maintenance release.