Here is the first proposed significant change to Jackson 3.x, from functionality perspective: I propose that `jackson-core` functionality for auto-detecting format of given input stream be removed, along with support `jackson-databind` has for exposing it.
Longer explanation, and tracking issue is here: https://github.com/FasterXML/jackson3-dev/issues/2 but the long and short of it is that: 1. As far as I know, this functionality is not widely used anywhere 2. Supporting functionality at databind level is cumbersome and prevents other changes (namely, https://github.com/FasterXML/jackson3-dev/issues/1) because of complexity of selecting from a set of ObjectMappers/ObjectReaders I will not go into details of how feature itself works, although anyone interested can find my original blog post at: http://www.cowtowncoder.com/blog/archives/2012/04/entry_472.html I am bit sad about letting go of this feature as I had high hopes for it originally -- it really works nicely for set of first 3 formats, json / Smile / xml -- but since it seems like all data format designers & their monkey thing it's great idea NOT to provide identifiable prefix (exception being Avro which does support proper magic cookie... if only for its file storage), its value has been less going forward. Further, I think it is possible to build such functionality in other ways that do not involve having to pipe it all the way through `JsonFactory` and up. Someone could instead build different kind of bootstrapper, externally; and we could build extension points to allow this. If(f) there's actual demand. So. I plan on proceeding with removal as I expect this to not be controversial. But I do want to give everyone a chance to voice their concerns, if any. -+ Tatu +- -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
