-
Notifications
You must be signed in to change notification settings - Fork 306
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
PAYARA-3110 Made TracedInterceptor serializable #3169
PAYARA-3110 Made TracedInterceptor serializable #3169
Conversation
This resolves a warning when persisting session scoped beans
Jenkins test please |
Quick build and test passed! |
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.
How do you reinstate the Bean Manager after the bean is retrieved from the session?
Jenkins test please |
Quick build and test passed! |
@Cousjava You could keep the TracedInterceptor serializable if you don't inject the BeanManager but use CDI.getBeanManager() whenever the BeanManager is needed. |
@smillidge @Cousjava @svendiedrichsen The concern regarding the bean manager is addressed by section 6.6.3 of the CDI spec:
See https://docs.jboss.org/cdi/spec/2.0-PFD/cdi-spec.html#passivation_capable_dependency |
Jenkins2 test please |
…store-error PAYARA-3110 Made TracedInterceptor serializable
This resolves a warning when persisting session scoped beans