July 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-135) Request parameter for terminating cid propagation

by Nicklas Karlsson (JIRA)

Request parameter for terminating cid propagation ------------------------------------------------- Key: CDI-135 URL: https://issues.jboss.org/browse/CDI-135 Project: CDI Specification Issues Issue Type: Feature Request Components: Contexts Affects Versions: 1.0 Reporter: Nicklas Karlsson The specification says the conversation id of non-transient conversations should be automatically propagated, it would however be handy to be able to stop this propagation on a per-component basis. If the request token (e.g. named "nocid") would be present, CDI would interpret this as if no cid was found in the request. This would enable users to jump from non-transient to non-transient conversations in one step (e.g. by using a commandLink with a f:param named nocid and an action that would start a new non-transient conversation. A further enhancement could be that the parameter value could be "end" and CDI would terminate the propagated non-transient conversation instead of just abandoning it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (CDI-142) Clarify behaviour of specializing beans across bean archive boundaries

by Stuart Douglas (JIRA)

Clarify behaviour of specializing beans across bean archive boundaries ---------------------------------------------------------------------- Key: CDI-142 URL: https://issues.jboss.org/browse/CDI-142 Project: CDI Specification Issues Issue Type: Clarification Reporter: Stuart Douglas For instance, if a bean in a war specializes a bean in an ejb jar does the bean in the war become visible to other bean archives that would not normally be able to see it? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (CDI-108) Align with release of @Inject included in the Java EE 7 platform

by Pete Muir (JIRA)

Align with release of @Inject included in the Java EE 7 platform ---------------------------------------------------------------- Key: CDI-108 URL: https://issues.jboss.org/browse/CDI-108 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir There is likely to be an update to JSR-330, @Inject, which we should align with. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (CDI-119) Standard way to obtain a BeanManager regardless of environment

by Cloves Almeida (JIRA)

Standard way to obtain a BeanManager regardless of environment -------------------------------------------------------------- Key: CDI-119 URL: https://issues.jboss.org/browse/CDI-119 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Cloves Almeida Priority: Minor As an alternative to #CDI-117: There should be a standard way to obtain a BeanManager instance regardless of environment. I propose a BeanManagerFactory that would implement the following resolution: 1) if in a JEE environment, use the JNDI resolution already proposed on spec 2) if in a non-JEE servlet container, use the servlet context attribute as proposed in #CDI-117 3) else, fallback on a "singleton" BeanManager For extensability, one could override the resolution mechanism by providing his own BeanManagerResolver. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (CDI-116) Add programmatic API to manipulate XML metadata

by Pete Muir (JIRA)

Add programmatic API to manipulate XML metadata ----------------------------------------------- Key: CDI-116 URL: https://issues.jboss.org/browse/CDI-116 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (CDI-133) Further clarify the notion of a decorated type

by Marius Bogoevici (JIRA)

Further clarify the notion of a decorated type ---------------------------------------------- Key: CDI-133 URL: https://issues.jboss.org/browse/CDI-133 Project: CDI Specification Issues Issue Type: Clarification Reporter: Marius Bogoevici Priority: Optional Essentially, remove the period between the first and second statement and use a single phrase instead: {quote} The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for <literal>java.io.Serializable</literal>. The decorator bean class and its superclasses are not decorated types of the decorator. {quote} This is a rather cosmetic change, but can improve the readability of the section. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Closed: (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 closed CDI-36. ------------------------ Resolution: Done > 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 > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-88) Fix ProcessObserverMethod javadoc to match spec

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-88?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-88. ------------------------ Resolution: Done > Fix ProcessObserverMethod javadoc to match spec > ----------------------------------------------- > > Key: CDI-88 > URL: https://issues.jboss.org/browse/CDI-88 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API, Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-85) Clarify use of "to" and "from" when refering to assignments in section 5.2.3

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-85?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-85. ------------------------ Resolution: Done > Clarify use of "to" and "from" when refering to assignments in section 5.2.3 > ---------------------------------------------------------------------------- > > Key: CDI-85 > URL: https://issues.jboss.org/browse/CDI-85 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-83) Clarify that BeanManager.createAnnotatedType() should return any modifications made by lifecycle events.

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-83?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-83. ------------------------ Resolution: Done > Clarify that BeanManager.createAnnotatedType() should return any modifications made by lifecycle events. > -------------------------------------------------------------------------------------------------------- > > Key: CDI-83 > URL: https://issues.jboss.org/browse/CDI-83 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev July 2011