Hi, this is basically already the case, despite that we have to align the possible factory method names. Currently it 0) it tries to lookup an explicit codec 1) it tries of, valueOf, instanceOf, getInstance. from, parse 2) it looks for a constructor taking a String argument 3) it throws a config exception
it uses toString for the opposite. That way with registering an explicit codec for a type you get full control, without the defaults apply as outlined.... Best, A Anatole Tresch <[email protected]> schrieb am So., 21. Dez. 2014 um 13:15: > +1 yes, makes sense! > Oliver B. Fischer <[email protected]> schrieb am So., 21. Dez. > 2014 um 12:21: > > I like the way the Jackson JSON processor uses annotations. You don’t >> need them, but if you need them you have a bunch of annoations to take >> over control. >> >> Am 21.12.14 um 12:09 schrieb Romain Manni-Bucau: >> >> > +1, that is what we did in Johnzon and it makes usage smooth IMO. >> > Le 21 déc. 2014 12:08, "Oliver B. Fischer" <[email protected]> >> a >> > écrit : >> > >> >> @Anatole: I would like to see this working even without any annotation >> by >> >> matching the bean property by its name with a configuration value. >> >> Annotations should be only needed if the default annotation free way >> is not >> >> working/is not flexible enough. >> >> >> >> WDYT? >> >> >> >> Bye, >> >> >> >> Oliver >> >> >> >> >> >> Am 18.12.14 um 00:05 schrieb Anatole Tresch: >> >> >> >> -- >> >> N Oliver B. Fischer >> >> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany >> >> P +49 30 44793251 >> >> M +49 178 7903538 >> >> E [email protected] >> >> S oliver.b.fischer >> >> J [email protected] >> >> X http://xing.to/obf >> >> >> >> >> >> >> -- >> N Oliver B. Fischer >> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany >> P +49 30 44793251 >> M +49 178 7903538 >> E [email protected] >> S oliver.b.fischer >> J [email protected] >> X http://xing.to/obf >> >>
