Why is 811 a problem? We can just ship jackson 1.9.x
On 11/3/2014 9:05 AM, Stian Thorgersen wrote:
Currently we only support Jackson, while WildFly now uses Jackson 2.
This is OK for our the auth-server itself, but could be more problematic for applications
(see
https://issues.jboss.org/browse/KEYCLOAK-811).
The main reason we can't use Jackson 2 is that they have changed the package for
annotations (@JsonProperty). I propose we get rid of all @JsonProperty and instead make
sure all fields are named correct and that we set the LowerCaseWithUnderscoresStrategy on
the ObjectMapper. This should also make it possible to use the Java classes with other
JSON libraries.
For example:
@JsonProperty("access_token")
protected String token;
@JsonProperty("jti")
protected String id;
Becomes:
protected String accessToken;
protected String jti;
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com