December 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-103) Support client controlled contexts

by Pete Muir (JIRA)

Support client controlled contexts ---------------------------------- Key: CDI-103 URL: https://issues.jboss.org/browse/CDI-103 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Pete Muir In a client controlled context, the client controls via some identifier (probably an identifier, but we should allow the context to inspect the injection point) which contextual instances it sees for a particular bean type. For example given: {code} @MyScope class Foo { String name; } {code} and a context which uses annotations to differentiate between contextual instance, these two injection points would see different instances: {code} @Inject @Bar Foo barFoo; @Inject @Baz Foo bazFoo; {code} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (CDI-160) Split specification into "core" and "Java EE integration"

by Pete Muir (JIRA)

Split specification into "core" and "Java EE integration" --------------------------------------------------------- Key: CDI-160 URL: https://issues.jboss.org/browse/CDI-160 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.1 (Proposed) Reporter: Pete Muir Assignee: Pete Muir Priority: Critical In order to better support implementations of CDI such as Weld SE and OpenWebBeans which are currently not certifiable by JSR-299 (as they don't implement any of the Java EE integrations) we should split the spec into core and Java EE integrations, and offer two modes within the TCK as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] (CDI-174) Define contexts and context lifecycle for Java SE

by Pete Muir (Created) (JIRA)

Define contexts and context lifecycle for Java SE ------------------------------------------------- Key: CDI-174 URL: https://issues.jboss.org/browse/CDI-174 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Pete Muir Fix For: 1.1 (Proposed) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-161) Java DSL to define beans to create and deploy

by Pete Muir (JIRA)

Java DSL to define beans to create and deploy --------------------------------------------- Key: CDI-161 URL: https://issues.jboss.org/browse/CDI-161 Project: CDI Specification Issues Issue Type: Feature Request Components: Packaging and Deployment Affects Versions: 1.0 Reporter: Pete Muir Fix For: 1.1 (Proposed) This would be especially useful in Java SE mode -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] (CDI-180) Clarify request context lifecycle during remote method invocation of EJB

by Martin Kouba (Created) (JIRA)

Clarify request context lifecycle during remote method invocation of EJB ------------------------------------------------------------------------ Key: CDI-180 URL: https://issues.jboss.org/browse/CDI-180 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba CDI 1.0 spec states in *6.7.1. Request context lifecycle*: "The request scope is active: during any remote method invocation of any EJB" and "The request context is destroyed: after the EJB remote method invocation" However it doesn't cover various invocation scenarios. For example it's possible to do in-VM invocation (via remote interface) from the same deployment or from a different deployment. Is the request context shared in this case? Will be destroyed after the EJB remote method invocation? Also take into account that application servers often do optimization and handle remote interface calls in a local interface manner within the same JVM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
13
0 / 0

[JBoss JIRA] Created: (CDI-143) Add a Util.getAnnotation(Member, Class<? extends Annotation>) style method

by Pete Muir (JIRA)

Add a Util.getAnnotation(Member, Class<? extends Annotation>) style method -------------------------------------------------------------------------- Key: CDI-143 URL: https://issues.jboss.org/browse/CDI-143 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Affects Versions: 1.0 Reporter: Pete Muir Fix For: 1.1 (Proposed) This would return information including stereotype information and is useful for other specs or frameworks to integrate with CDI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-109) Invalid beans should not be injectable into extensions

by John Ament (JIRA)

Invalid beans should not be injectable into extensions ------------------------------------------------------ Key: CDI-109 URL: https://issues.jboss.org/browse/CDI-109 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament Currently, you can inject beans that may not be ready yet into the extension's call back methods. As an example, I can inject something application scoped like this in to an extension, but it should really be throwing a definition exception (or similar): public void handleABD(@Observes AfterBeanDiscovery abd, MyApplicationScopedBean masb) { } Pete had noted that really the only safe thing to inject, other than the observed call back, is the bean manager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

10
18
0 / 0

[JBoss JIRA] (CDI-183) Clarify that CDI.current() can be called by anyone and not just CDI extensions

by Emmanuel Bernard (Created) (JIRA)

Clarify that CDI.current() can be called by anyone and not just CDI extensions ------------------------------------------------------------------------------ Key: CDI-183 URL: https://issues.jboss.org/browse/CDI-183 Project: CDI Specification Issues Issue Type: Clarification Reporter: Emmanuel Bernard Fix For: 1.1 (Proposed) http://docs.jboss.org/cdi/spec/1.1.EDR1/html/spi.html#provider EDR1 makes it a bit unclear that this is allowed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-151) Remove from section 6.7 JMS notes

by John Ament (JIRA)

Remove from section 6.7 JMS notes --------------------------------- Key: CDI-151 URL: https://issues.jboss.org/browse/CDI-151 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament In section 6.7, a reference is made to JMS Message Listeners. MessageListeners (as bound to the consumers) are not available in JMS in an EE environment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
9
0 / 0

[JBoss JIRA] (CDI-187) Clarify serializability requirements for interceptors/decorators

by Jozef Hartinger (Created) (JIRA)

Clarify serializability requirements for interceptors/decorators ---------------------------------------------------------------- Key: CDI-187 URL: https://issues.jboss.org/browse/CDI-187 Project: CDI Specification Issues Issue Type: Clarification Components: Contexts, Decorators, Interceptors Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1.EDR2 The spec says: {quote}A managed bean is passivation capable if and only if the bean class is serializable and all interceptors and decorators of the bean *are serializable*.{quote} The "interceptors and decorators of the bean *are serializable*" part is problematic. While it is fine to examine the defining class in case of standard interceptors/decorators, the question is: How to find out whether an extension-provided interceptor/decorator in serializable? It does not make sense to check the implementation of the Interceptor/Decorator interfaces nor to examine the class returned by Bean.getBeanClass() as that would break the abstraction. IMHO, the spec should say that: {quote}A managed bean is passivation capable if and only if the bean class is serializable and all interceptors and decorators of the bean are *passivation capable*.{quote} Where a standard interceptor/decorator would be passivation capable if and only if it implemented the Serializable interface whereas the following section of the spec would handle extension-provided interceptors/decorators. {quote}A custom implementation of Bean is passivation capable if it implements the interface PassivationCapable. An imple- mentation of Contextual that is not a bean is passivation capable if it implements both PassivationCapable and Serial- izable. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2011