February 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-38) Send servlet events as CDI events

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-38?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-38: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Send servlet events as CDI events > --------------------------------- > > Key: CDI-38 > URL: https://issues.jboss.org/browse/CDI-38 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events, Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > > Seam Servlet provide these as well -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-24) Make it easier to build passivating contexts by making sure Contextual objects passed to them are serializable

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-24?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-24: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Make it easier to build passivating contexts by making sure Contextual objects passed to them are serializable > -------------------------------------------------------------------------------------------------------------- > > Key: CDI-24 > URL: https://issues.jboss.org/browse/CDI-24 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > > OWB ensures that any Contextual impl passed to a passivating context is serializable, making it much easier to impl a custom passivating context. We should probably make this required by the spec. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-80) Support conversations in Servlet

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-80?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-80: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Support conversations in Servlet > -------------------------------- > > Key: CDI-80 > URL: https://issues.jboss.org/browse/CDI-80 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-97) Ability to process modules

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-97?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-97: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Ability to process modules > -------------------------- > > Key: CDI-97 > URL: https://issues.jboss.org/browse/CDI-97 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-23) Allow BeanManager to be resolved as though you were in another bean archive

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-23?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-23: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Allow BeanManager to be resolved as though you were in another bean archive > --------------------------------------------------------------------------- > > Key: CDI-23 > URL: https://issues.jboss.org/browse/CDI-23 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions, Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > > Currently it's not possible to access beans as though you were in another bean manager, something that is useful for extensions to be able to do. For example, if I want to create a facade over the ELResolver, or access a particular configuration bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-36) ObserverMethod.notify() does not forward qualifiers for Event

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-36?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-36: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > ObserverMethod.notify() does not forward qualifiers for Event > ------------------------------------------------------------- > > Key: CDI-36 > URL: https://issues.jboss.org/browse/CDI-36 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Jordan Ganoff > Fix For: 1.1 (Proposed) > > > There's currently no way to get the qualifiers for a fired event. ObserverMethod.notify() only passes the event object itself. Without the qualifiers it is difficult to bridge the gap between CDI events and some other event infrastructure (e.g. JMS). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-84) Non EE modules should be able to trigger creation of a BeanManager

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-84?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-84: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Non EE modules should be able to trigger creation of a BeanManager > ------------------------------------------------------------------ > > Key: CDI-84 > URL: https://issues.jboss.org/browse/CDI-84 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Fix For: 1.1 (Proposed) > > > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > Where EE modules are defined to be; ejb-jar, rar, client jar and war. > This is a missmatch between the EE spec and the CDI spec. According to the CDI spec, any archive with a beans.xml is defined as a BeanArchive and should be included in a BeanManager, EE define it to be only EE modules should trigger BeanManager creation. > Opening this up to follow the CDI spec will let any library use the BeanManager to introspect other BeanArchives without having to involve the owning EE module in the loop. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-29?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-29: ------------------------- Fix Version/s: 1.1 (Proposed) (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: 1.1 (Proposed) > > > 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 is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-42) Allow you to inject the intercepted bean into an Interceptor

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-42?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-42: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > Allow you to inject the intercepted bean into an Interceptor > ------------------------------------------------------------ > > Key: CDI-42 > URL: https://issues.jboss.org/browse/CDI-42 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Interceptors > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-49) The availability of the BeanManager should follow the normal EE visibility rules

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-49?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-49: ------------------------- Fix Version/s: 1.1 (Proposed) (was: TBD) > The availability of the BeanManager should follow the normal EE visibility rules > -------------------------------------------------------------------------------- > > Key: CDI-49 > URL: https://issues.jboss.org/browse/CDI-49 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment, Resolution > Affects Versions: 1.0 > Environment: JSR-000316 Java Platform, Enterprise Edition 6 Specification > Reporter: Aslak Knutsen > Fix For: 1.1 (Proposed) > > > EE 6 spec > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > In e.g. a EAR deployment, a WAR module can see a EJB module. With CDI enabled in the EJB, the WAR can only see the BeanManager if the WAR itself is also CDI enabled. In cases where you want to do dynamic introspection of available beans etc, this is a bit cumbersome, especially since the introspecting code can be in a packaged jar inside a unknown WAR.. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev February 2011