Skip to content

Consider removing use of global default TypeFactory.defaultInstance() #1373

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 Sep 15, 2016 · 1 comment
Closed
Labels
duplicate Duplicate of an existing (usually earlier) issue

Comments

@cowtowncoder
Copy link
Member

(See #1363 for background)

While it is convenient to start with a shareable TypeFactory for ObjectMapper, using static singleton accessed through TypeFactory.createInstance(), this can lead to unintentional Class retention for app servers (et al) that support hot reloading. It may be relatively easy to just force construction of a new TypeFactory for new ObjectMappers, which would remove this problem.

@cowtowncoder cowtowncoder added the 3.x Issues to be only tackled for Jackson 3.x, not 2.x label Jul 17, 2018
@cowtowncoder
Copy link
Member Author

Implemented via #4659 -- closing this as dup (despite being older, the other included in release notes)

@cowtowncoder cowtowncoder closed this as not planned Won't fix, can't repro, duplicate, stale Dec 1, 2024
@cowtowncoder cowtowncoder added duplicate Duplicate of an existing (usually earlier) issue and removed 3.x Issues to be only tackled for Jackson 3.x, not 2.x labels Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate of an existing (usually earlier) issue
Projects
None yet
Development

No branches or pull requests

1 participant