-
Notifications
You must be signed in to change notification settings - Fork 106
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
default typing fails on 2.7.0 - 2.8.2-SNAPSHOT #94
Comments
I can confirm this. It gets better when you use other values from I'm in a situation where I have to use My solution was to wrap the call to |
@digulla Now that |
Sorry, I mean For the array types, Jackson produces this JSON: My guess is that there is still some code lurking somewhere which catches types that JavaScript supports natively. Suggestion: Add unit tests which serialize and deserialize all types (arrays and lists) or all kinds of bultin Java types. When you can serialize it, there should also be a way to deserialize it without telling Jackson the expected type. |
@digulla This sounds more like something related to core Jackson databinding. As to type information addition is not hard-coded (there is nothing directly special about either arrays or So it is necessary to choose typing value that includes type you want to apply type id for. As to testing: there is plenty of testing for all kinds of types. But at this point extension of test coverage will happen by way of addressing reported problems, or via contributions. I am still not sure there is anything wrong wrt this handling, but if a test case can be provided, an issue for |
Below is the same as ForceLazyLoadingTest, with added enableDefaultTyping().
Result during
Map<?,?> stuff = mapper.readValue(json, Map.class);
(and it is not because of the PersistentCollections, as I am working on replacing them and the result is the same with java.util.* collections):The text was updated successfully, but these errors were encountered: