Skip to content

Problem with NamingStrategy, creator methods with implicit names #806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cowtowncoder opened this issue May 28, 2015 · 3 comments
Closed
Labels
2.18 Issues planned at 2.18 or later property-discovery Problem with property discovery (introspection)
Milestone

Comments

@cowtowncoder
Copy link
Member

Just a reference to FasterXML/jackson-module-parameter-names#18 since this is most likely a problem with databind and not the parameter names access module.

@cowtowncoder
Copy link
Member Author

I can reproduce this, but it is not an easy problem to fix. The problem is that whereas with @JsonCreator properties get detected early, so that POJOPropertiesCollector can apply name mangling. without that annotation properties are only added to the map at a later stage, when doing more thorough introspection.

So: a problem to be fixed. But not a quick one to fix.

cowtowncoder added a commit that referenced this issue May 30, 2015
@cowtowncoder cowtowncoder added 3.x Issues to be only tackled for Jackson 3.x, not 2.x and removed 2.9 labels May 4, 2017
@cowtowncoder
Copy link
Member Author

And just to clarify earlier note (since I had forgotten and had to re-learn this): inclusion of @JsonCreator will work around the issue, so this is due to renaming being performed at wrong phase, relative to processing.

@cowtowncoder
Copy link
Member Author

Fixed via #4515 for inclusion in 2.18.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.18 Issues planned at 2.18 or later property-discovery Problem with property discovery (introspection)
Projects
None yet
Development

No branches or pull requests

1 participant