try/catch usage of sql classes in serializer static initializer to al… #1073
Conversation
…low it to be used in embedded compact1 configurations.
|
Hmmh ok. Do you have specific case in mind where this has been problematic? I don't doubt it can happen, but it would be good to have that as sort of documentation. I assume this is not for Android, as no problem with these types has been reported before. |
|
@claudemt Thanks again -- I changed this slightly, to happen within One thing to note: while it is checked in 2.5 branch, merged forward, there are no plans for more full 2.5 releases. It is possible micro-patches (like 2.5.5-1) may still be released for critical problems. So most likely this will be first available in 2.6.5 and 2.7.0 releases. |
|
Thanks a lot for this quick merge. Your changes appear to be fine. |
|
@claudemt Ok thank you for the update. For what it is worth, 2.7.0 is being released now. I realize it may not be feasible for you to upgrade at this point, but if it is, that would be the quickest upgrade route. |
# By Tatu Saloranta (113) and others # Via Tatu Saloranta * 'master' of https://github.com/FasterXML/jackson-databind: (124 commits) Minor addition related to FasterXML#1087: resolve context type, assuming type bindings from that are expected to work. Add unit test for FasterXML#999 minor warnings cleanup Add Javadoc badge with automatic version detection Fix FasterXML#1083 Add failing test for FasterXML#1083 add a unit test to verify that Object Id works via AtomicReference too Minor javadoc improvement wrt FasterXML#1076, making `SimpleType.construct(Class)` deprecated (was not yet, for some reason, should have been) Fix FasterXML#1078 Fix FasterXML#1079 [maven-release-plugin] prepare for next development iteration [maven-release-plugin] prepare release jackson-databind-2.7.0 prepare for 2.7.0 final Fix FasterXML#1073 Try to reproduce FasterXML#1074 javadoc trimming Try to reproduce FasterXML#825 again, still passes. minor improvement to ensure base64 encoding uses configured setting Undo part of change done for StringDeserializer; caused issues with XML handling further minor cleanups to cleanup ...
…low it to be used in embedded compact1 configurations.
try/catch usage of sql classes in serializer static initializer to allow it to be used in embedded compact1 configurations.
The fix I made is quite simple but maybe you would prefer to have an externally specified factory that only instantiates a subset of the concrete type serializers. But that would require a substantial change since the existing serializers (BeanSerializerFactory/BasicSerializerFactory) do not allow much customization.