[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991566#comment-14991566
]
Falko Modler commented on DELTASPIKE-1018:
------------------------------------------
One problem here is that the JMX stuff is located in the
{{deltaspike-core-impl}} module which does not have/must not have an dependency
on {{deltaspike-cdictrl-api}}.
This could be solved by moving the JMX stuff to a new module (e.g.
{{deltaspike-jmx}}) which then would have an (optional?) dependency on
{{deltaspike-cdictrl-api}}.
> 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)
