Well, my primary issue is that the dependency for JAX-RS is marked as required currently (JIRA/PR submitted). However, I'm a big fan of the single responsibility principle. The JSON-B jar should merely implement the JSON-B spec (IMHO). I realize moving things around in jar files breaks folks, so I get why we wouldn't want to move it in 1.1.2, but we should consider it when we can break things.
On Sat, Jun 24, 2017 at 3:19 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi James > > Not sure i get what you ask. The provider is here but the api is not - > shouldnt be at least - mandatory normally. > > On 1.1 we can move it back to jaxrs module cause we dont have the java > version constraint as for 1.0 branch - which is partially why it was here. > That said we will miss jsonb in jaxrs and you can have the same complaint > then. > > Idea was also not to have to import 2 dependencies for it to work - just > import jsonb - and you can also disable it in servers so not fully sure > what is the actual issue :s. > > > > Le 24 juin 2017 08:45, "James Carman" <ja...@carmanconsulting.com> a > écrit : > > > While it is a common use case that folks would use JSON-B for JAX-RS > > payload serialization/deserialization, it is not the only use case. > > Perhaps we can move this provider class out of the jsonb jar and remove > the > > dependency? > > >
