I found Johnzon to work very well in a large scale app for a MSO. It was handling millions of transactions a day with only 2 VMs talking to customer set top boxes and handling Geo fencing (millions of calls as well on the same servers). It handled marshalling/unmarshalling of objects with limited coding.
On Fri, Mar 31, 2017 at 10:56 AM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi François, > > jackson has a few more advanced feature but I'll say a word on it at the > end. > In term of perf it is a bit faster but if you use it for JAXRS then HTTP is > so slow compared to json roundtrip than you dont care of which provider you > use (in term of scale). > jackson has more binding support, the most known are yaml and jaxb...but > that's out of json > > Now johnzon is jsonp based, very light and Apache powered compared to > jackson (to answer to the implicit "why johnzon in tomee"). > > About the first point: most of the very advanced features are due to a lack > of modelling of the json model so before jumping on them you should ask > yourself: do I need it or am I messing up my app? in 80% of the case it is > the last one from experience. > > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://blog-rmannibucau.rhcloud.com> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2017-03-31 16:39 GMT+02:00 COURTAULT Francois < > francois.courta...@gemalto.com>: > > > Hello, > > > > Any reason to prefer Jackson instead of Johnzon (default JAX-RS provider > > in TomEE 7.x ) like: > > > > - Performance > > > > - Functionality (@JsonInclude, @JsonIgnoreProperties with no > > equivalence in Johnzon) > > > > - Others .... > > ? > > > > Best Regards. > > ________________________________ > > This message and any attachments are intended solely for the addressees > > and may contain confidential information. Any unauthorized use or > > disclosure, either whole or partial, is prohibited. > > E-mails are susceptible to alteration. Our company shall not be liable > for > > the message if altered, changed or falsified. If you are not the intended > > recipient of this message, please delete it and notify the sender. > > Although all reasonable efforts have been made to keep this transmission > > free from viruses, the sender will not be liable for damages caused by a > > transmitted virus. > > > -- Steven P. Goldsmith
