-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom JSON marshaller #335
Comments
Closed
lhazlewood
added a commit
that referenced
this issue
Jul 11, 2018
lhazlewood
added a commit
that referenced
this issue
Jul 11, 2018
lhazlewood
added a commit
that referenced
this issue
Jul 11, 2018
lhazlewood
added a commit
that referenced
this issue
Jul 11, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JJWT's internal Jackson marshaller is ... internal. It can't be modified or replaced by JJWT users.
This issue represents the work to:
Create a new
JsonConverter
(or similarly named) interface. Instances of this interface perform the JSON work.Create multiple maven modules in the JJWT project. The current code would go under a new module,
jjwt-core
. orjjwt-api
(haven't decided yet).Create a new maven module
jjwt-orgjson
as the default implementation of theJsonConverter
interface using theorg.json
APIs (these are only ~ 50k of size compared tojackson-core
's 360k, and Android already hasorg.json
support, so no need to include that dependency in those environments.Create a new maven module
jjwt-jackson
that uses the Jackson API to implementJsonConverter
for people that like using Jackson.Create a new maven module
jjwt
that is nothing more than a dependency of (jjwt-core
|jjwt-api
) andjjwt-orgjson
to ensure anyone depending on justjjwt
gets JJWT with the default json parser.Allow specifying the
JsonConverter
onJwtParser
andJwtBuilder
instances to allow users to choose whatever JSON implementation they want.If a user doesn't specify a
JwtConverter
go through class/env discovery logic to find and use the first one available, if possible.The text was updated successfully, but these errors were encountered: