Simplest would just be to do Jackson2 only. Would mean we'd need to have a
Jackson2 module for EAP6 subsystem. For other adapters it's just a
dependency so shouldn't matter.
On 13 January 2016 at 15:55, Bill Burke <bburke(a)redhat.com> wrote:
Can't make it pluggable as it relies on annotations.
On 1/13/2016 9:06 AM, Stian Thorgersen wrote:
Now that we no longer need to support EAP 6.4 on the server side we can
upgrade to Jackson2, which is supposed to be significantly faster than
Jackson.
Question - Can we require Jackson2 for adapters as well? Or should we make
JSON serialization support on the adapter side pluggable somehow? Or should
we support both Jackson and Jackson2 on the adapter side.
_______________________________________________
keycloak-dev mailing
listkeycloak-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red
Hathttp://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev