January 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-169) Remove the 'No type variable in event objects' restriction

by Stuart Douglas (JIRA)

Remove the 'No type variable in event objects' restriction ---------------------------------------------------------- Key: CDI-169 URL: https://issues.jboss.org/browse/CDI-169 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Stuart Douglas CDI 10.1 states: An event object is an instance of a concrete Java class with no type variables. ... An event type may not contain a type variable. Which seems silly considering the container fires events with a type variable at startup. I can't think of any reason why this should be prohibited. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

8
15
0 / 0

[JBoss JIRA] (CDI-176) Clarify why EL name is not allowed when declaring resource

by Martin Kouba (Created) (JIRA)

Clarify why EL name is not allowed when declaring resource ---------------------------------------------------------- Key: CDI-176 URL: https://issues.jboss.org/browse/CDI-176 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba CDI 1.0 spec states in section *3.5.1. Declaring a resource*: "If the producer field declaration specifies an EL name, the container automatically detects the problem and treats it as a definition error." Is there any reason to forbid EL name for declared resource? -- 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

3
3
0 / 0

[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] 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-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] (CDI-213) Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction

by Martin Kouba (JIRA)

Martin Kouba created CDI-213: -------------------------------- Summary: Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction Key: CDI-213 URL: https://issues.jboss.org/browse/CDI-213 Project: CDI Specification Issues Issue Type: Clarification Components: Events Reporter: Martin Kouba Priority: Minor At the moment, the specification does not really specify what happens if an observer method does directly initiate, commit or rollback JTA transaction. See *10.5. Observer notification*: "An observer method may not directly initiate, commit or rollback JTA transactions." -- 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

4
11
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, 3 months

10
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2012