Yep, this is traced in release notes. Basically from jettison we miragted
to johnzon to have a better json mapping and moreover a mapping closer to
jsonb spec which will come and to not rely on jaxb.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-05-31 16:12 GMT+02:00 tam <[email protected]>:

> I'll try to isolate the error. Roughly, I'm sending a JSON structure for an
> entire application object (my Module from the example above) from the
> client
> to the server where I have the PUT method from the example. Neither of the
> JSON attributes are mapped to the Module parameter, so an empty Java object
> is created and inserted in the database. But at that point, the called
> service doesn't provide any error log, so I have no idea whether the
> deserialization is called at all, can't interpret the JSON structure, or
> whatever. All I know is that it works with the old library setup on 1.7.4
> that I sent you in my original question. So there appear to be
> compatibility
> issues between different implementations of JAX-RS.
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/JsonGenerationException-after-migrating-to-7-0-0-tp4678684p4678693.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Reply via email to