[jira] [Resolved] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-1018.
--
Resolution: Won't Fix
please contact the users-list, if you need help with the suggested solution.
> 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)
[jira] [Commented] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991607#comment-14991607
]
Gerhard Petracek commented on DELTASPIKE-1018:
--
you can just write your own interceptor and apply it autom. once you find
@JmxManaged.
we can't do it in ds-core, because cdi-ctrl is mainly for java-se based
applications. it works with some ee-servers, but not with all of them and
therefore it isn't completely portable in view of ee-servers until ~ee8.
> 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)
[jira] [Commented] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Created] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
Falko Modler created DELTASPIKE-1018:
Summary: 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)
[jira] [Commented] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14992169#comment-14992169
]
Gerhard Petracek commented on DELTASPIKE-1018:
--
+1 and also thx for providing new ideas! that's very welcome!
you are also welcome to discuss such ideas on our users and/or dev list!
> 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)
[jira] [Commented] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14992178#comment-14992178
]
Romain Manni-Bucau commented on DELTASPIKE-1018:
[~gpetracek] why not providing such an interceptor in DS:
{code}
@MBean // no change
@CdiContextActivator({RequestScoped.class, MyScoped.class}) // new feature
public class MyMBean {}
{code}
can be in cdictrl module
> 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)
[jira] [Updated] (DELTASPIKE-1019) Enterprise container friendlier deltaspike-cdictrl-weld
[
https://issues.apache.org/jira/browse/DELTASPIKE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-1019:
-
Attachment: DELTASPIKE-1019.patch
> Enterprise container friendlier deltaspike-cdictrl-weld
> ---
>
> Key: DELTASPIKE-1019
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1019
> Project: DeltaSpike
> Issue Type: Improvement
> Components: CdiControl
>Affects Versions: 1.0.2
>Reporter: Falko Modler
>Assignee: Mark Struberg
>Priority: Minor
> Attachments: DELTASPIKE-1019.patch
>
>
> h5. Preface
> Although {{deltaspike-cdictrl}} was designed for "SE setups",
> {{ContextControl}} can be used in an enterprise CDI container like WELD on
> JBoss/Wildfly just fine. {{CdiControl}} cannot be used.
> h5. Problem
> Even when you do not use {{CdiControl}}, enterprise WELD will at least log
> {{ClassNotFoundException}} regarding {{org.jboss.weld.environment.se.Weld}}
> when {{deltaspike-cdictrl-weld}} is deployed.
> In WAR-deployments you might be able to exclude {{WeldContainerControl}} via
> {{beans.xml}} but with EAR-deployments you are out of luck.
> h5. Solution
> - *Either* exclude {{WeldContainerControl}} (is created via {{ServiceLoader}}
> anyway):
> {code:xml|title=deltaspike-cdictrl-weld/META-INF/beans.xml}
>
> {code}
> PS: Not sure whether {{@Typed()}} would work as well?
> - *Or* provide a second assembly of {{deltaspike-cdictrl-weld}} with some
> classifer like "ctxctrl-only" which does not include the {{CdiControl}} stuff
> I think the {{beans.xml}}-approach is the better solution.
> h5. Workaround
> Custom re-packing/shading of {{deltaspike-cdictrl-weld}} and possibly also
> {{deltaspike-cdictrl-api}}. Very cumbersome...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-1019) Enterprise container friendlier deltaspike-cdictrl-weld
[
https://issues.apache.org/jira/browse/DELTASPIKE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek resolved DELTASPIKE-1019.
--
Resolution: Fixed
Fix Version/s: 1.5.2
> Enterprise container friendlier deltaspike-cdictrl-weld
> ---
>
> Key: DELTASPIKE-1019
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1019
> Project: DeltaSpike
> Issue Type: Improvement
> Components: CdiControl
>Affects Versions: 1.0.2
>Reporter: Falko Modler
>Assignee: Mark Struberg
>Priority: Minor
> Fix For: 1.5.2
>
> Attachments: DELTASPIKE-1019.patch
>
>
> h5. Preface
> Although {{deltaspike-cdictrl}} was designed for "SE setups",
> {{ContextControl}} can be used in an enterprise CDI container like WELD on
> JBoss/Wildfly just fine. {{CdiControl}} cannot be used.
> h5. Problem
> Even when you do not use {{CdiControl}}, enterprise WELD will at least log
> {{ClassNotFoundException}} regarding {{org.jboss.weld.environment.se.Weld}}
> when {{deltaspike-cdictrl-weld}} is deployed.
> In WAR-deployments you might be able to exclude {{WeldContainerControl}} via
> {{beans.xml}} but with EAR-deployments you are out of luck.
> h5. Solution
> - *Either* exclude {{WeldContainerControl}} (is created via {{ServiceLoader}}
> anyway):
> {code:xml|title=deltaspike-cdictrl-weld/META-INF/beans.xml}
>
> {code}
> PS: Not sure whether {{@Typed()}} would work as well?
> - *Or* provide a second assembly of {{deltaspike-cdictrl-weld}} with some
> classifer like "ctxctrl-only" which does not include the {{CdiControl}} stuff
> I think the {{beans.xml}}-approach is the better solution.
> h5. Workaround
> Custom re-packing/shading of {{deltaspike-cdictrl-weld}} and possibly also
> {{deltaspike-cdictrl-api}}. Very cumbersome...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14992410#comment-14992410
]
Romain Manni-Bucau commented on DELTASPIKE-1018:
I saw the interceptor often enough to think it can be a built in feature.
> 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)
[jira] [Created] (DELTASPIKE-1019) Enterprise container friendlier deltaspike-cdictrl-weld
Falko Modler created DELTASPIKE-1019:
Summary: Enterprise container friendlier deltaspike-cdictrl-weld
Key: DELTASPIKE-1019
URL: https://issues.apache.org/jira/browse/DELTASPIKE-1019
Project: DeltaSpike
Issue Type: Improvement
Components: CdiControl
Affects Versions: 1.0.2
Reporter: Falko Modler
Priority: Minor
h5. Preface
Although {{deltaspike-cdictrl}} was designed for "SE setups",
{{ContextControl}} can be used in an enterprise CDI container like WELD on
JBoss/Wildfly just fine. {{CdiControl}} cannot be used.
h5. Problem
Even when you do not use {{CdiControl}}, enterprise WELD will at least log
{{ClassNotFoundException}} regarding {{org.jboss.weld.environment.se.Weld}}
when {{deltaspike-cdictrl-weld}} is deployed.
In WAR-deployments you might be able to exclude {{WeldContainerControl}} via
{{beans.xml}} but with EAR-deployments you are out of luck.
h5. Solution
- *Either* exclude {{WeldContainerControl}} (is created via {{ServiceLoader}}):
{code:xml|title=deltaspike-cdictrl-weld/META-INF/beans.xml}
{code}
PS: Not sure whether {{@Typed()}} would work as well?
- *Or* provide a second assembly of {{deltaspike-cdictrl-weld}} with some
classifer like "ctxctrl-only" which does not include the {{CdiControl}} stuff
I think the {{beans.xml}}-approach is the better solution.
h5. Workaround
Custom re-packing/shading of {{deltaspike-cdictrl-weld}} and possibly also
{{deltaspike-cdictrl-api}}. Very cumbersome...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991772#comment-14991772
]
Falko Modler commented on DELTASPIKE-1018:
--
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)
[jira] [Updated] (DELTASPIKE-1019) Enterprise container friendlier deltaspike-cdictrl-weld
[
https://issues.apache.org/jira/browse/DELTASPIKE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Falko Modler updated DELTASPIKE-1019:
-
Description:
h5. Preface
Although {{deltaspike-cdictrl}} was designed for "SE setups",
{{ContextControl}} can be used in an enterprise CDI container like WELD on
JBoss/Wildfly just fine. {{CdiControl}} cannot be used.
h5. Problem
Even when you do not use {{CdiControl}}, enterprise WELD will at least log
{{ClassNotFoundException}} regarding {{org.jboss.weld.environment.se.Weld}}
when {{deltaspike-cdictrl-weld}} is deployed.
In WAR-deployments you might be able to exclude {{WeldContainerControl}} via
{{beans.xml}} but with EAR-deployments you are out of luck.
h5. Solution
- *Either* exclude {{WeldContainerControl}} (is created via {{ServiceLoader}}
anyway):
{code:xml|title=deltaspike-cdictrl-weld/META-INF/beans.xml}
{code}
PS: Not sure whether {{@Typed()}} would work as well?
- *Or* provide a second assembly of {{deltaspike-cdictrl-weld}} with some
classifer like "ctxctrl-only" which does not include the {{CdiControl}} stuff
I think the {{beans.xml}}-approach is the better solution.
h5. Workaround
Custom re-packing/shading of {{deltaspike-cdictrl-weld}} and possibly also
{{deltaspike-cdictrl-api}}. Very cumbersome...
was:
h5. Preface
Although {{deltaspike-cdictrl}} was designed for "SE setups",
{{ContextControl}} can be used in an enterprise CDI container like WELD on
JBoss/Wildfly just fine. {{CdiControl}} cannot be used.
h5. Problem
Even when you do not use {{CdiControl}}, enterprise WELD will at least log
{{ClassNotFoundException}} regarding {{org.jboss.weld.environment.se.Weld}}
when {{deltaspike-cdictrl-weld}} is deployed.
In WAR-deployments you might be able to exclude {{WeldContainerControl}} via
{{beans.xml}} but with EAR-deployments you are out of luck.
h5. Solution
- *Either* exclude {{WeldContainerControl}} (is created via {{ServiceLoader}}):
{code:xml|title=deltaspike-cdictrl-weld/META-INF/beans.xml}
{code}
PS: Not sure whether {{@Typed()}} would work as well?
- *Or* provide a second assembly of {{deltaspike-cdictrl-weld}} with some
classifer like "ctxctrl-only" which does not include the {{CdiControl}} stuff
I think the {{beans.xml}}-approach is the better solution.
h5. Workaround
Custom re-packing/shading of {{deltaspike-cdictrl-weld}} and possibly also
{{deltaspike-cdictrl-api}}. Very cumbersome...
> Enterprise container friendlier deltaspike-cdictrl-weld
> ---
>
> Key: DELTASPIKE-1019
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1019
> Project: DeltaSpike
> Issue Type: Improvement
> Components: CdiControl
>Affects Versions: 1.0.2
>Reporter: Falko Modler
>Priority: Minor
>
> h5. Preface
> Although {{deltaspike-cdictrl}} was designed for "SE setups",
> {{ContextControl}} can be used in an enterprise CDI container like WELD on
> JBoss/Wildfly just fine. {{CdiControl}} cannot be used.
> h5. Problem
> Even when you do not use {{CdiControl}}, enterprise WELD will at least log
> {{ClassNotFoundException}} regarding {{org.jboss.weld.environment.se.Weld}}
> when {{deltaspike-cdictrl-weld}} is deployed.
> In WAR-deployments you might be able to exclude {{WeldContainerControl}} via
> {{beans.xml}} but with EAR-deployments you are out of luck.
> h5. Solution
> - *Either* exclude {{WeldContainerControl}} (is created via {{ServiceLoader}}
> anyway):
> {code:xml|title=deltaspike-cdictrl-weld/META-INF/beans.xml}
>
> {code}
> PS: Not sure whether {{@Typed()}} would work as well?
> - *Or* provide a second assembly of {{deltaspike-cdictrl-weld}} with some
> classifer like "ctxctrl-only" which does not include the {{CdiControl}} stuff
> I think the {{beans.xml}}-approach is the better solution.
> h5. Workaround
> Custom re-packing/shading of {{deltaspike-cdictrl-weld}} and possibly also
> {{deltaspike-cdictrl-api}}. Very cumbersome...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (DELTASPIKE-1018) Automatic RequestScope activation for @MBean invocations
[
https://issues.apache.org/jira/browse/DELTASPIKE-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
