Yes, that makes sense; we could also remove the tooling assistance - and let any kind of class be provided (but the parser will insist on our abstraction or a jackson-specific object).

Finally, I don't know enough about Jackson2 and its compatibility with Jackson1. I agree we should default to Jackson2 if both are on the classpath, but I also think we might need the option to __force__ the use of Jackson1 if both are available.

WDYT?