Hi Mike, Since it is pluggable yes but the side notes are:
1. YAML generator/parsers are not consistent even if there is a kind of spec and it iq quite error prone (see all the mess around k8s and the wrapper to not manipulate yaml directly) 2. It is not a pure json AFAIK but an OSGi flavor with comments (not even the Johnzon built-in flavor - C-style - but a spec version) so good to stay aligned on the spec and felix IMO Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mer. 22 juil. 2020 à 08:42, Mike Hummel <m...@mhus.de> a écrit : > Hello, > > it would be more common to use yaml instead of json for human readable > configurations... > > Is this an option? > > Best Regards, > > Mike > > > On 8. Jul 2020, at 08:49, Jean-Baptiste Onofre <j...@nanthrax.net> wrote: > > > > Hi, > > > > Yes, it’s feature support in json format. Inner parser is Johnson (but > pluggable). > > > > Regards > > JB > > > >> Le 8 juil. 2020 à 08:41, Steinar Bang <s...@dod.no> a écrit : > >> > >> Thanks for the update, JB! > >> > >> Out of curiosity: What's "Features JSON"? Karaf features to pull in JSON > >> support? If so, which parser? Jackson? GSON? Something else...? > >> > >> Thanks! > >> > >> > >> - Steinar > >> > > > >
