Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When using withFactory on ObjectMapper, the created Factory has a TypeParser which still has the original Factory #894

Closed
lufegit opened this issue Aug 12, 2015 · 1 comment
Closed

When using withFactory on ObjectMapper, the created Factory has a TypeParser which still has the original Factory #894

lufegit opened this issue Aug 12, 2015 · 1 comment
Milestone
2.6.2

Comments

@lufegit
Copy link
Contributor

lufegit commented Aug 12, 2015

The result of this situation is that the ClassLoader which is passed to the new Factory is not used by TypeParser (who has the original ClassLoader-less factory still), resulting on failure to find the classes on TypeParser even though the new Factory has the correct ClassLoader. I'm sending a pull request to change this.
lufegit pushed a commit to lufegit/jackson-databind that referenced this issue Aug 12, 2015
Fix FasterXML#894 - derived TypeFactory (instantiated using with... m…
bf54c00 
…ethod) should have a new TypeParser which points to itself
@lufegit lufegit mentioned this issue Aug 12, 2015
Closed
@cowtowncoder cowtowncoder added this to the 2.6.2 milestone Aug 14, 2015
@cowtowncoder
Copy link
Member

Ok, I solved the problem using the idea, just slightly different form. I hope I did not miss anything; please let me know if I did overlook something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.6.2
Development

No branches or pull requests
2 participants
@cowtowncoder @lufegit