why cxf doesn't use jackson? i don't know...everybody uses it in real life. Probably because they use jaxb as main API so the bridge to jettison was quite easy and light.
The issue? just return an attribute with an url "http://foo.com"; and you'll get "http:\/\/foo.com". This is escaped so low in the layers you can't avoid it (and no boolean or custom stuff to do easily). Moreover the marshalling is too closed to jaxb to be easy (management of list, map etc...). Since json is a lot used with js clients it never really matches (this one is not a bug but not a really nice default). I'm ok to keep jettison for this release (1.5.2) then to choose (or not) for 1.6.0 jackson (the issue of including it would be app overriding...probably another potential shade :s). *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/1/13 David Blevins <david.blev...@gmail.com> > > On Jan 13, 2013, at 1:56 PM, David Blevins <david.blev...@gmail.com> > wrote: > > > > > On Jan 13, 2013, at 12:32 PM, David Blevins <david.blev...@gmail.com> > wrote: > > > >> > >> 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. > > > > Interestingly enough the built-in vm impl appears to be faster on the > unmarshal. Getting encoding errors on the marshal though. Digging into it. > > Never mind, my IDE classpath as 3 copies of woodstocks, 2 of jettison and > of course the built-in vm version (intellij's maven support doesn't really > manage the classpath like maven does). Let me clean up and try again. > > > -David > >
