On Jan 13, 2013, at 9:34 AM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote:
> two questions about next release and dependencies: > 1) David reworked our JavaEE descriptors parsing to use sxc. In this > refactoring we now use woodstox under the stax api (was it mandatory?) > -> do we want it? if yes do we shade it or simply skip it in the > classloader to avoid classloader issues if an app provides it? (+ 500ko > about) Digging in the SXC code to see how tightly woodstox is integrated. > 2) same kind of question about jackson. In two work jackson is THE library > to do JSon. It is very friendly for JAXRS. Currently we use default > providers of cxf. We saw a bunch of users switching it to jackson. I tested > the default one and got some issues we can't workaround (one bothering > thing is the fact the string values are escaped by jettison and that's too > low level to be changed, so basically you never have what you expect after > marshalling). > -> do we want to keep default providers of cxf or do we switch to a real > implementation (ie jackson, +1.2M about) Can you expand on the String issue with jettison. Is there actually a bug there and people just don't care? Kind of curious why CXF doesn't use Jackson by default if it is so amazing. -David
