October 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-248) Provide means to observe a group of qualified events ("Qualifier Inheritance"?)

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-248?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-248: ------------------------------------- Fix Version/s: TBD (was: 2.0 (discussion)) > Provide means to observe a group of qualified events ("Qualifier Inheritance"?) > -------------------------------------------------------------------------------- > > Key: CDI-248 > URL: https://issues.jboss.org/browse/… [View More]CDI-248 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Events > Reporter: Jens Schumann > Fix For: TBD > > > We have been using CDI events for application development quite extensively. For instance we use events to propagate entity lifecycle events (@Created/@Updated/@Deleted Customer customer) or GUI selections (@Selected/@Deselected Customer customer) and implement related business logic in event observers. (e.g. send email for newly created customers, clear cached values on select/deselect/create/update/delete ...). > This works quite well, however we have noticed that especially our JSF Presentation Tier contains lots of observer methods implementing the same behavior for a group of related CDI events. > Example: > {code} > public class XyzBean { > public void onCustomerCreate(@Observes @Created Customer customer) { reset();} > public void onCustomerUpdate(@Observes @Updated Customer customer) { reset();} > public void onCustomerDelete(@Observes @Deleted Customer customer) { reset();} > > } > {code} > Looks ugly, doesn't it? > The above example could be improved if CDI would be able to observe a group of qualified events, e.g. public void onCustomerLifeCycleEvent(@Observes @LifeCycleChange Customer customer) { reset(); } - ignore method and qualifier names for now. > Since Java does not support annotation inheritance grouping could be achieved using "qualified qualifier annotations": > {code} > @Qualifier > public @interface LifeCycleChange > @Qualifier > @LifeCycleChange > public @interface Created > @Qualifier > @LifeCycleChange > public @interface Updated > @Qualifier > @LifeCycleChange > public @interface Deleted > @Qualifier > public @interface SelectionChange > @Qualifier > @SelectionChange > public @interface Selected > @Qualifier > @SelectionChange > public @interface Deselected > {code} > WDYT? Side effects? Problems? -- This message was sent by Atlassian JIRA (v6.4.11#64026) [View Less]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-248) Provide means to observe a group of qualified events ("Qualifier Inheritance"?)

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-248?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-248: ------------------------------------- Priority: Minor (was: Major) > Provide means to observe a group of qualified events ("Qualifier Inheritance"?) > -------------------------------------------------------------------------------- > > Key: CDI-248 > URL: https://issues.jboss.org/browse/CDI-248 > Project: … [View More]CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Events > Reporter: Jens Schumann > Priority: Minor > Fix For: TBD > > > We have been using CDI events for application development quite extensively. For instance we use events to propagate entity lifecycle events (@Created/@Updated/@Deleted Customer customer) or GUI selections (@Selected/@Deselected Customer customer) and implement related business logic in event observers. (e.g. send email for newly created customers, clear cached values on select/deselect/create/update/delete ...). > This works quite well, however we have noticed that especially our JSF Presentation Tier contains lots of observer methods implementing the same behavior for a group of related CDI events. > Example: > {code} > public class XyzBean { > public void onCustomerCreate(@Observes @Created Customer customer) { reset();} > public void onCustomerUpdate(@Observes @Updated Customer customer) { reset();} > public void onCustomerDelete(@Observes @Deleted Customer customer) { reset();} > > } > {code} > Looks ugly, doesn't it? > The above example could be improved if CDI would be able to observe a group of qualified events, e.g. public void onCustomerLifeCycleEvent(@Observes @LifeCycleChange Customer customer) { reset(); } - ignore method and qualifier names for now. > Since Java does not support annotation inheritance grouping could be achieved using "qualified qualifier annotations": > {code} > @Qualifier > public @interface LifeCycleChange > @Qualifier > @LifeCycleChange > public @interface Created > @Qualifier > @LifeCycleChange > public @interface Updated > @Qualifier > @LifeCycleChange > public @interface Deleted > @Qualifier > public @interface SelectionChange > @Qualifier > @SelectionChange > public @interface Selected > @Qualifier > @SelectionChange > public @interface Deselected > {code} > WDYT? Side effects? Problems? -- This message was sent by Atlassian JIRA (v6.4.11#64026) [View Less]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-270) Allow @WithAnnotations to be applied to other events

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-270?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-270: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Allow @WithAnnotations to be applied to other events > ---------------------------------------------------- > > Key: CDI-270 > URL: https://issues.jboss.org/browse/CDI-270 > Project: CDI … [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-279) Provide CDI SPI that could be used to directly replace java.lang.reflect methods for expanding the use of @Stereotype to Java EE 7 platform

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-279?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-279: ------------------------------------- Priority: Minor (was: Major) > Provide CDI SPI that could be used to directly replace java.lang.reflect methods for expanding the use of @Stereotype to Java EE 7 platform > ------------------------------------------------------------------------------------------------------------------------------------------- > > … [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-279) Provide CDI SPI that could be used to directly replace java.lang.reflect methods for expanding the use of @Stereotype to Java EE 7 platform

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-279?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-279: ------------------------------------- Fix Version/s: TBD (was: 2.0 (discussion)) > Provide CDI SPI that could be used to directly replace java.lang.reflect methods for expanding the use of @Stereotype to Java EE 7 platform > ------------------------------------------------------------------------------------------------------------------------… [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-280) clarify usage of 'bean' term usage in the spec

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-280?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-280: ------------------------------------- Priority: Minor (was: Major) > clarify usage of 'bean' term usage in the spec > ---------------------------------------------- > > Key: CDI-280 > URL: https://issues.jboss.org/browse/CDI-280 > Project: CDI Specification Issues > Issue Type: Clarification > … [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-280) clarify usage of 'bean' term usage in the spec

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-280?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-280: ------------------------------------- Fix Version/s: TBD (was: 2.0 (discussion)) > clarify usage of 'bean' term usage in the spec > ---------------------------------------------- > > Key: CDI-280 > URL: https://issues.jboss.org/browse/CDI-280 > Project: CDI Specification Issues > … [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-291) Clarify interceptor/decorator resolution rules

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-291?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-291: ------------------------------------- Fix Version/s: TBD (was: 2.0 (discussion)) > Clarify interceptor/decorator resolution rules > ---------------------------------------------- > > Key: CDI-291 > URL: https://issues.jboss.org/browse/CDI-291 > Project: CDI Specification Issues > … [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-362) No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-362: ------------------------------------- Fix Version/s: TBD (was: 2.0 (discussion)) > No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting > --------------------------------------------------------------------------------------------- > > Key: CDI-362 > URL: https:/… [View More]

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-362) No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-362: ------------------------------------- Priority: Minor (was: Major) > No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting > --------------------------------------------------------------------------------------------- > > Key: CDI-362 > URL: https://issues.jboss.org/browse/CDI-362 &… [View More]

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev October 2016