October 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-20) @Observes(propagate = false) - stop event propagation after being handled by an observer

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-20?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand closed CDI-20. ----------------------------------- Resolution: Rejected Kills the idea of decoupling behind event. And BTW throwing an exception in a synchronous observer can do the trick. > @Observes(propagate = false) - stop event propagation after being handled by an observer > ---------------------------------------------------------------------------------------- > > Key: CDI-20 > URL: https://issues.jboss.org/browse/CDI-20 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Environment: any > Reporter: Walter White > Fix For: 2.0 (discussion) > > > I would like to have the ability to stop event propagation after it is handled by any observer only for certain situations. Is it possible to add a property to the annotation indicating whether the propagation should continue after being handled by the observer? Alternatively, would it be more concise to add a qualifier annotation which specifies the propagation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-21) Support PostConstruct callbacks in Extension class

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-21?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand closed CDI-21. ----------------------------------- Resolution: Rejected {{@BeforeBeanDiscovery}} is nearly the equivalent of {{@PostConstruct}} from the extension inititlisation POV. > Support PostConstruct callbacks in Extension class > -------------------------------------------------- > > Key: CDI-21 > URL: https://issues.jboss.org/browse/CDI-21 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Sivakumar Thyagarajan > Priority: Minor > Fix For: 2.0 (discussion) > > > It is sometimes useful to get to know after a portable extension class has been instantiated, so that the state of the Extension could be initialized [ie not establishing state in the constructor and having it called twice when the Extension is proxied]. Though the 1.0 specification does not require this, it would be useful to support @PostConstruct callback on Extension class in the next version of the specification. > Please see https://jira.jboss.org/browse/WELD-713 for additional information on this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-29) Method of accessing contexts regardless of active state

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-29?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-29: ------------------------------------ Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Method of accessing contexts regardless of active state > ------------------------------------------------------- > > Key: CDI-29 > URL: https://issues.jboss.org/browse/CDI-29 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Nicklas Karlsson > Fix For: 2.1 (Discussion) > > > It would be practical to have a way of accessing contexts from the BeanManager regardless of their active state. Currently, contexts cannot be activated (e.g. Conversation) in a portable way because there is no way of getting the inactive context in order to activate it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-37) Stateless scope

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-37?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-37: ------------------------------------ Fix Version/s: TBD (was: 2.0 (discussion)) > Stateless scope > --------------- > > Key: CDI-37 > URL: https://issues.jboss.org/browse/CDI-37 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Adam Warski > Fix For: TBD > > > From a discussion on weld-dev (http://lists.jboss.org/pipermail/weld-dev/2011-January/002825.html): > Here's my use-case: > I have some beans which are inherently stateless, e.g. "services" or factory methods. The only fields they have are injected. I am using these beans in normal-scoped passivation-capable beans, e.g. session or conversation scoped. In such case, they also have to be passivation-capable, which means either > (a) be normal-scoped (proxyable) > (b) implement Serializable and leave the bean dependent-scoped > If I go with (a) this means that I'd have to put my bean in the request, session, conversation or application scope. However none of these choices make much sense, as they indicate the my beans holds request/session/etc-scoped data - which it doesn't, as it is stateless. > So I am left with (b) - implement Serializable + dependent scope. But is that the right thing to do always? Firstly, if I have a lot of such stateless beans, which are injected one into another, serializing a simple session-scope bean may mean that half the beans in my application get serialized. Secondly, a developer looking at such a bean could wonder why is this bean serializable? Esp if it doesn't have any state? > Hence what I'd like in fact is a proxyable scope (normal), which on serialization would only write the proxy information, on de-serialization would inject a new instance of the bean (or from a pool), and on injection would either behave as dependent (new instance), or take beans from a pool. Just as the EJB Stateless scope (except that I don't want to make my bean an EJB). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-45) Optional Injection Points

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-45: ------------------------------------ Priority: Optional (was: Major) > Optional Injection Points > ------------------------- > > Key: CDI-45 > URL: https://issues.jboss.org/browse/CDI-45 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Affects Versions: 1.0 > Reporter: Stuart Douglas > Priority: Optional > Fix For: TBD > > > There are occoasions where it may be useful for some injection points to be optional, e.g. > @Inject > @Optional > MyBean bean; > This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-45) Optional Injection Points

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-45: ------------------------------------ Fix Version/s: TBD (was: 2.0 (discussion)) > Optional Injection Points > ------------------------- > > Key: CDI-45 > URL: https://issues.jboss.org/browse/CDI-45 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: TBD > > > There are occoasions where it may be useful for some injection points to be optional, e.g. > @Inject > @Optional > MyBean bean; > This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-61) Producers and beans that are under construction

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-61?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-61: ------------------------------------ Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Producers and beans that are under construction > ----------------------------------------------- > > Key: CDI-61 > URL: https://issues.jboss.org/browse/CDI-61 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 2.1 (Discussion) > > > I think we need the spec to say something about cases where an injection point of a bean resolves to a producer method of the same bean. The implementation should detect that this is a definition error. It shouldn't try to call a producer method on a non-fully-initialized bean. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-63) Add section on cyclic dependencies to the spec

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-63?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-63: ------------------------------------ Fix Version/s: TBD (was: 2.0 (discussion)) > Add section on cyclic dependencies to the spec > ---------------------------------------------- > > Key: CDI-63 > URL: https://issues.jboss.org/browse/CDI-63 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans, Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-89) Add @Unwraps from Seam Solder

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-89?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-89: ------------------------------------ Fix Version/s: TBD (was: 2.0 (discussion)) > Add @Unwraps from Seam Solder > ------------------------------ > > Key: CDI-89 > URL: https://issues.jboss.org/browse/CDI-89 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Stuart Douglas > Assignee: Pete Muir > Fix For: TBD > > > @Unwraps allows for an essentially stateless scope for producer methods and fields. > At injection time a dependent scoped proxy is injected into the injection point. When a methods is invoked on this proxy it calls the corresponding @Unwraps methods to get the instance to invoke the method on. > Because the proxy is @Dependent scoped, the @Unwraps method can inject the corresponding InjectionPoint. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-79) Allow you to inspect the decorator chain

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-79?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-79: ------------------------------------ Fix Version/s: TBD (was: 2.0 (discussion)) > Allow you to inspect the decorator chain > ---------------------------------------- > > Key: CDI-79 > URL: https://issues.jboss.org/browse/CDI-79 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev October 2016