July 2014 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-26) Bootstrap API for CDI

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-26?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-26: ------------------------------------ Fix Version/s: 2.0 (discussion) (was: TBD) > Bootstrap API for CDI > --------------------- > > Key: CDI-26 > URL: https://issues.jboss.org/browse/CDI-26 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 2.0 (discussion) > > > Weld and other CDI impls allow an embedded mode. > See http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#... for example -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 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.0 (discussion) (was: TBD) > 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.0 (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.2.6#6264)

9 years, 9 months

1
0
0 / 0

[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 commented on CDI-20: ----------------------------------------- That means that we have a big discussion on events for CDI 2.0, because the question becomes even worse if we introduce asynchronous events: CDI-31 ;) > @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.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-25) Support @Inject FacesContext facesContext;

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-25?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand resolved CDI-25. ------------------------------------- Resolution: Won't Fix Things to be done in JSF > Support @Inject FacesContext facesContext; > ------------------------------------------ > > Key: CDI-25 > URL: https://issues.jboss.org/browse/CDI-25 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

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

by Jens Schumann (JIRA)

[ https://issues.jboss.org/browse/CDI-20?page=com.atlassian.jira.plugin.sys... ] Jens Schumann commented on CDI-20: ---------------------------------- Good point, Antoine. And even with ordered event observers: What would be the meaning of "propagate = false" for transactional event observers? > @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.2.6#6264)

9 years, 9 months

1
0
0 / 0

[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 commented on CDI-20: ----------------------------------------- Useless if observer are not ordered > @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.2.6#6264)

9 years, 9 months

1
0
0 / 0

[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 updated CDI-20: ------------------------------------ Fix Version/s: 2.0 (discussion) (was: TBD) > @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.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-19) Ordering execution on Extensions

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-19?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand commented on CDI-19: ----------------------------------------- IMO no extension ordering but SPI observers ordering if we provide a solution for CDI-4 > Ordering execution on Extensions > -------------------------------- > > Key: CDI-19 > URL: https://issues.jboss.org/browse/CDI-19 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Robson Ximenes > Priority: Minor > Fix For: 2.0 (discussion) > > > I believe the cdi portable extension could have the load order of extensions the same as it is registered; > It is possible that one extension expect some previous preparation of beans from another extension -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-16) Improve EE 6 Managed Bean integration

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-16?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand closed CDI-16. ----------------------------------- Fix Version/s: (was: TBD) Resolution: Won't Fix Nothing to do on CDI side > Improve EE 6 Managed Bean integration > ------------------------------------- > > Key: CDI-16 > URL: https://issues.jboss.org/browse/CDI-16 > Project: CDI Specification Issues > Issue Type: Tracker > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > > Try to work out if we can improve on this. > At least, we should clarify what happens if a CDI managed bean is annotated with @ManagedBean -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-19) Ordering execution on Extensions

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-19?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-19: ------------------------------------ Fix Version/s: 2.0 (discussion) (was: TBD) > Ordering execution on Extensions > -------------------------------- > > Key: CDI-19 > URL: https://issues.jboss.org/browse/CDI-19 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Robson Ximenes > Priority: Minor > Fix For: 2.0 (discussion) > > > I believe the cdi portable extension could have the load order of extensions the same as it is registered; > It is possible that one extension expect some previous preparation of beans from another extension -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev July 2014