Skip to content
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

Allow override default RedisSerializer #283

Closed
rwinch opened this issue Aug 31, 2015 · 8 comments
Closed

Allow override default RedisSerializer #283

rwinch opened this issue Aug 31, 2015 · 8 comments
Assignees
Labels
in: redis type: enhancement A general enhancement
Milestone

Comments

@rwinch
Copy link
Member

rwinch commented Aug 31, 2015

When using @EnableRedisHttpSession you can now override the default RedisSerializer by specifying a bean with the name of defaultRedisSerializer.

@fehmicansaglam
Copy link

@rwinch I am trying to use Jackson2JsonRedisSerializer but I could not make it work. Is this feature already released or should I wait for the next release?

@pcornelissen
Copy link

You need the brixton build-snapshot

@fehmicansaglam
Copy link

Thanks. Is there a roadmap for the next stable release?

@rwinch
Copy link
Member Author

rwinch commented Feb 4, 2016

@fehmicansaglam From a Spring Session perspective you should only need 1.1.0.M1. Can you provide more details on how this is not working?

@fehmicansaglam
Copy link

Milestone works but it was not clear that this feature was not supported in
the stable release.
On Thu, 4 Feb 2016 at 18:54, Rob Winch notifications@github.com wrote:

@fehmicansaglam https://github.com/fehmicansaglam From a Spring Session
perspective you should only need 1.1.0.M1. Can you provide more details on
how this is not working?


Reply to this email directly or view it on GitHub
#283 (comment)
.

Fehmi Can Saglam

@rwinch
Copy link
Member Author

rwinch commented Feb 4, 2016

@fehmicansaglam Glad to hear it works in 1.1.0.M1.

This issue has 1.1.0.M1 as the selected milestone. Can you clarify why it wasn't clear you needed 1.1.0.M1 (perhaps something else made this misleading)?

@fehmicansaglam
Copy link

I am not sure. It was possibly my bad.

On 4 February 2016 at 19:32:04, Rob Winch (notifications@github.com) wrote:

@fehmicansaglam Glad to hear it works in 1.1.0.M1.

This issue has 1.1.0.M1 as the selected milestone. Can you clarify why it wasn't clear
you needed 1.1.0.M1 (perhaps something else made this misleading)?


Reply to this email directly or view it on GitHub:
#283 (comment)

@rwinch
Copy link
Member Author

rwinch commented Feb 4, 2016

@fehmicansaglam Thanks for the fast response. Not a problem it happens. I just wanted to make sure that there wasn't something we could do to make this more clear. Thanks again for your feedback!

@rwinch rwinch added type: enhancement A general enhancement in: redis labels Feb 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: redis type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

3 participants