[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991772#comment-14991772
]
Falko Modler edited comment on DELTASPIKE-1018 at 11/5/15 3:12 PM:
-------------------------------------------------------------------
We already use such an interceptor. I can also understand that you won't fix
it. At least people can now find this ticket clearly pointing out the "issue".
Thanks for the quick feedback
was (Author: famod):
We already use such an interceptor. I can also understand that you won't fix
it. At least people can now find this ticket clearly pointing out the "issue.
Thanks for the quick feedback
> Automatic RequestScope activation for @MBean invocations
> ---------------------------------------------------------
>
> Key: DELTASPIKE-1018
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1018
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0.2
> Reporter: Falko Modler
> Priority: Minor
>
> When a {{@JmxManaged}} method is called (via jconsole for instance) on a
> CDI-Bean which has been registered as a MBean via {{@MBean}} annotation, the
> RequestScope is not active.
> It would be handy if RequestScope could be actived automatically, perhaps
> configurable via a new {{@MBean}} attribute and/or
> {{apache-deltaspike.properties}}.
> Workaround: Implement and register an Interceptor which actives/deactivates
> the scope via {{ContextControl}} around the method invocation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
