December 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-659) Introduce a provider in-specific servlet listener

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-659?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-659: --------------------------------- Well I would say the general problem is that spec doesn't talk about any Servlet container integration at all. > Introduce a provider in-specific servlet listener > ------------------------------------------------- > > Key: CDI-659 > URL: https://issues.jboss.org/browse/CDI-659 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Reporter: John Ament > Fix For: 2.1 (Discussion) > > > Currently, each provider (OWB, Weld) provides a servlet listener for registering CDI in a plain servlet container. Looking at other specs, e.g. JAX-RS, references to an implementation in-specific way to register your services are provided. We should do the same for CDI, allowing a user to register a servlet listener without needing to leverage provider-specific classes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-661) Annotated should return AnnotatedElement

by John Ament (JIRA)

John Ament created CDI-661: ------------------------------ Summary: Annotated should return AnnotatedElement Key: CDI-661 URL: https://issues.jboss.org/browse/CDI-661 Project: CDI Specification Issues Issue Type: Feature Request Components: Javadoc and API Reporter: John Ament The {{Annotated}} interface returns a {{Type}} for its base type. It should return an {{AnnotatedElement}} based on its naming - since annotations are derived from {{AnnotatedElement}}s not from {{Type}}s -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-661) Annotated should return AnnotatedElement

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-661?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-661: --------------------------- Description: The {{Annotated}} interface returns a {{Type}} for its base type. It should return an {{AnnotatedElement}} based on its naming - since annotations are derived from {{AnnotatedElement}} s not from {{Type}} s (was: The {{Annotated}} interface returns a {{Type}} for its base type. It should return an {{AnnotatedElement}} based on its naming - since annotations are derived from {{AnnotatedElement}}s not from {{Type}}s) > Annotated should return AnnotatedElement > ---------------------------------------- > > Key: CDI-661 > URL: https://issues.jboss.org/browse/CDI-661 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Javadoc and API > Reporter: John Ament > > The {{Annotated}} interface returns a {{Type}} for its base type. It should return an {{AnnotatedElement}} based on its naming - since annotations are derived from {{AnnotatedElement}} s not from {{Type}} s -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-660) Registration of custom Producer

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-660?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-660: --------------------------- Fix Version/s: 2.1 (Discussion) > Registration of custom Producer > ------------------------------- > > Key: CDI-660 > URL: https://issues.jboss.org/browse/CDI-660 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans, Portable Extensions > Reporter: John Ament > Fix For: 2.1 (Discussion) > > > Introduce a feature that would allow a developer to register a custom producer, probably in a portable extension as a lifecycle method, separate from a custom bean implementation. > The producer would have optional access to the underlying injection point (which bean does not provide) but probably needs to still track: > - Qualifiers > - Scope -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-660) Registration of custom Producer

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-660?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-660: --------------------------- Description: Introduce a feature that would allow a developer to register a custom producer, probably in a portable extension as a lifecycle method, separate from a custom bean implementation. The producer would have optional access to the underlying injection point (which bean does not provide) but probably needs to still track: - Qualifiers - Scope was: Introduce a feature that would allow a developer to register a custom producer, separate from a custom bean implementation. The producer would have optional access to the underlying injection point (which bean does not provide) but probably needs to still track: - Qualifiers - Scope > Registration of custom Producer > ------------------------------- > > Key: CDI-660 > URL: https://issues.jboss.org/browse/CDI-660 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans, Portable Extensions > Reporter: John Ament > > Introduce a feature that would allow a developer to register a custom producer, probably in a portable extension as a lifecycle method, separate from a custom bean implementation. > The producer would have optional access to the underlying injection point (which bean does not provide) but probably needs to still track: > - Qualifiers > - Scope -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-660) Registration of custom Producer

by John Ament (JIRA)

John Ament created CDI-660: ------------------------------ Summary: Registration of custom Producer Key: CDI-660 URL: https://issues.jboss.org/browse/CDI-660 Project: CDI Specification Issues Issue Type: Feature Request Components: Beans, Portable Extensions Reporter: John Ament Introduce a feature that would allow a developer to register a custom producer, separate from a custom bean implementation. The producer would have optional access to the underlying injection point (which bean does not provide) but probably needs to still track: - Qualifiers - Scope -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-659) Introduce a provider in-specific servlet listener

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-659?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-659: --------------------------- Fix Version/s: 2.1 (Discussion) > Introduce a provider in-specific servlet listener > ------------------------------------------------- > > Key: CDI-659 > URL: https://issues.jboss.org/browse/CDI-659 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Reporter: John Ament > Fix For: 2.1 (Discussion) > > > Currently, each provider (OWB, Weld) provides a servlet listener for registering CDI in a plain servlet container. Looking at other specs, e.g. JAX-RS, references to an implementation in-specific way to register your services are provided. We should do the same for CDI, allowing a user to register a servlet listener without needing to leverage provider-specific classes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-659) Introduce a provider in-specific servlet listener

by John Ament (JIRA)

John Ament created CDI-659: ------------------------------ Summary: Introduce a provider in-specific servlet listener Key: CDI-659 URL: https://issues.jboss.org/browse/CDI-659 Project: CDI Specification Issues Issue Type: Feature Request Components: Java EE integration Reporter: John Ament Currently, each provider (OWB, Weld) provides a servlet listener for registering CDI in a plain servlet container. Looking at other specs, e.g. JAX-RS, references to an implementation in-specific way to register your services are provided. We should do the same for CDI, allowing a user to register a servlet listener without needing to leverage provider-specific classes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-658) Introduce ProducerConfigurator

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-658: ---------------------------------------- Summary: Introduce ProducerConfigurator Key: CDI-658 URL: https://issues.jboss.org/browse/CDI-658 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 2.0-EDR2 Reporter: Antoine Sabot-Durand Configurator API lacks {{ProducerConfigurator}} it should be accessible from a new version of {{ProcessProducer.setProducer()}} method -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-593) Mention javax.enterprise.inject.spi.Prioritized in spec text and improve its javadoc

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-593?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-593: ---------------------------------------- Assignee: Antoine Sabot-Durand > Mention javax.enterprise.inject.spi.Prioritized in spec text and improve its javadoc > ------------------------------------------------------------------------------------ > > Key: CDI-593 > URL: https://issues.jboss.org/browse/CDI-593 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Assignee: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > * javadoc would definitely deserve some more info > * the spec text should mention this interface as well and describe basic use cases (e.g. an interceptor passed to {{AfterBeanDiscovery.addBean()}} and implementing this interface is globally enabled) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2016