Usage of api client #76
Comments
dehora
added a commit
that referenced
this issue
Nov 18, 2015
This changes the initialization on demand holder for ObjectMapper to configure the mapper once. Previously the mapper was being created once but reconfigured on each access. Fix for #76
dehora
added a commit
that referenced
this issue
Nov 18, 2015
This changes the initialization on demand holder for ObjectMapper to configure the mapper once. Previously the mapper was being created once but reconfigured on each access. Fix for #76
|
@cristianciutea thanks for reporting this. the loading was changed in #79 to stop reconfiguring the mapper, and is available in version 1.3.0-b3 if you want to give it a try. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How should I use the api client. For example if I want to find a user by id, I do this:
User.find(id);
But from what I can tell, this call configures and registers a new jackson ObjectMapper module instance that is always the same. Why do we do this? I'm asking because I have a problem that after I do many api calls those objects remain stored in memory and the program stops with out of memory exception.
The text was updated successfully, but these errors were encountered: