Internals: in general you do builder.setAccessMode(accessMode); but in jsonb context we didnt wire it yet cause we enforce JsonbAccessMode but we can surely still expose it (in particular read from jsonbconfig properties the delegate).
Spec: In jsonb we have @JsonbCreator support for constructors. 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-06-24 14:19 GMT+02:00 James Carman <[email protected]>: > Are there docs on how to provide my own AccessMode implementation? > > > > On Sat, Jun 24, 2017 at 8:16 AM Romain Manni-Bucau <[email protected]> > wrote: > > > Using a custom accessmode you can. > > > > Side note: we have constructor support I think. > > > > Le 24 juin 2017 13:59, "James Carman" <[email protected]> a > > écrit : > > > > > Current, with Johnzon, I can't instantiate objects for classes where I > > have > > > no default constructor available. With GSON, it supports this using > the > > > Unsafe class I believe. Is there a way for me to provide my own > > > instantiator implementation (I'd probably pick Objenesis)? I don't > want > > to > > > have to provide default constructors for all of my immutable "request" > > > objects when using Johnzon in my JAX-RS MessageBodyReader/ > > > MessageBodyWriter. > > > > > > Thanks, > > > > > > James > > > > > >
