March 2012 - cdi-dev - Jboss List Archives

[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, 4 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, 4 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, 4 months

1
2
0 / 0

[JBoss JIRA] (CDI-217) JMX support in CDI managed environments

by Tim de Buhr (JIRA)

Tim de Buhr created CDI-217: ------------------------------- Summary: JMX support in CDI managed environments Key: CDI-217 URL: https://issues.jboss.org/browse/CDI-217 Project: CDI Specification Issues Issue Type: Feature Request Components: Java SE Integration Affects Versions: 1.0 Reporter: Tim de Buhr get support of @Inject by using MBeanServer managed MBean/MXBean objects. Example: To get the number of all processed jobs just use @Produces at a method like getTotalCount() and use @Inject in the MBean implementation to get the count value -- 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

3
4
0 / 0

[JBoss JIRA] (CDI-216) @Veto and ProcessAnnotatedType

by Gerhard Petracek (JIRA)

Gerhard Petracek created CDI-216: ------------------------------------ Summary: @Veto and ProcessAnnotatedType Key: CDI-216 URL: https://issues.jboss.org/browse/CDI-216 Project: CDI Specification Issues Issue Type: Clarification Components: Concepts, Packaging and Deployment Affects Versions: 1.1.EDR1 Reporter: Gerhard Petracek Priority: Critical currently the spec. specifies: "The container must fire an event for each Java class or interface it discovers in a bean archive, and for annotated type added by BeforeBeanDiscovery.addAnnotatedType(), before it reads the declared annotations." that's ok for cdi 1.0. however, if @Veto gets added to cdi 1.1, we need a clarification here. the internal implementation via a std. cdi doesn't make sense because other extensions still get the corresponding ProcessAnnotatedType event. -> Annotated types with @Veto (or as suggested at CDI-50: @Unmanaged or @Exclude) shouldn't lead to a ProcessAnnotatedType event. -- 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

3
4
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

LJC comments/questions

by Luigi Bitonti

Hi All, My name is Luigi Bitonti and I am a member of the London Java Community (LJC). We are interested in the CDI 1.1 specification and would like to help by contributing our point of view as developers. We are also keen to help with any tasks you feel like assigning to us. We have read the latest draft specification and put together a first round of comments and questions: All the discussions and development are being tracked on Jira (https://issues.jboss.org/browse/CDI). The whole process seems very transparent and easy to follow which is a very good thing. We view very positively the adoption of JCP 2.8. It looks like there is also a private mailing list the EG uses. Is that in use? What's its purpose? It looks like good work is being done and some interesting new addition have already made it into this new version of the specification, such as: - CDI-86 Support firing general purpose lifecycle events in Java EE environments - CDI-129 Clarify behaviour of @ApplicationScoped in EARs What we would like to see going forward is an "easier and clearer" specification, so the current efforts seem to be going in the right direction. Hopefully more good proposals will be implemented as part of the final version. The lack of clear separation between the SE and EE parts of the specification seems to be an issue that limits adoption. This is also related to the lack of a standard way of bootstrapping the DI container in SE. In this respect we believe the following planned changes will bring improvements: - CDI-160 Split the specification into "Core" and "EE integrations". - CDI-26 Provide a bootstrap API for the CDI container outside of an EE container. Do you think these will make it into CDI 1.1? Other interesting proposals we would like to see implemented are: - CDI-139 Support for unmanaged instances. - CDI-110 Provide support for binding an invocation handler to an interface or abstract class - CDI-30 An API for managing built in contexts I've noticed the first 2 have been voted at the top of the most popular issues. I suppose they are very likely to make it into CDI 1.1. Is that correct? Regarding the following issue, we have a question: - CDI-51 Support static injection Static injection would still not be allowed for final fields, just as for the non-static case, right? Thanks for all your work on the specification. I hope we'll be able to help your efforts going forward. Cheers, Luigi

12 years, 4 months

4
7
0 / 0

[JBoss JIRA] (CDI-201) Reflect BeanAttributes within validation rules

by Jozef Hartinger (Created) (JIRA)

Reflect BeanAttributes within validation rules ---------------------------------------------- Key: CDI-201 URL: https://issues.jboss.org/browse/CDI-201 Project: CDI Specification Issues Issue Type: Clarification Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) For example: 1) The spec says: {quote}Each child <class> element must specify the name of an alternative bean class. If there is no class with the specified name, or *if the class with the specified name is not an alternative bean class, the container automatically detects the problem and treats it as a deployment problem*. {quote} Since that "alternative" attribute of a bean can be altered by a portable extension in the ProcessBeanAttributes phase, the specification should instead require for each class listed in the <class> element, each bean that defines the class as its bean class is an alternative. 2) {quote}If Y has a name and X declares a name explicitly, using @Named, the container automatically detects the problem and treats it as a definition error.{quote} The specification should abstract from @Named, since the ProcessBeanAttributes enables an extension to set a bean name without using @Named Likely, there are other similar issues. -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2012