-
Notifications
You must be signed in to change notification settings - Fork 1k
fix-1641: serialization concerns (1) #2062
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
Conversation
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
| } | ||
|
|
||
| @Override | ||
| @Cacheable("serviceinstances") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should start with all services being non-cacheable and I will work in reverse, to add cacheable separate clients.
Removing this option is a breaking change, but adding separate clients on top, would be not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets separate removing the cachable annotations into its own PR to keep things a bit cleaner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, done.
|
@ryanjbaxter this is part-1 of some other PRs that will eventually close issue 1641. I will let you know when that issue is completely covered. This is now ready to be looked at, thank you. |
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
No description provided.