March 2013 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-52: ------------------------------------ Also, the spec says: {quote} the injection point is a disposer method parameter then no +Bean+ instance can be injected, as a disposer method may resolve to more than one producer method. {quote} which is not quite in line with the rest of the spec. The spec should again either say that an injected parameter of type Bean<?> on a disposer method is either: * a definition problem * non-portable > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Blocker > Fix For: 1.1.FD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger updated CDI-52: ------------------------------- Fix Version/s: 1.1.FD (was: 1.1.PFD) Priority: Blocker (was: Critical) > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Blocker > Fix For: 1.1.FD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger reopened CDI-52: -------------------------------- The changes were reverted which brought unclear wording again to the spec again. The spec should state the if a disposer method defines an injection point of type InjectionPoint and qualifier @Default, this is either: * a definition problem * non-portable > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 1.1.PFD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-354) Inappropriate payload of the @Initialized(ConversationScoped.class) event

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-354: ----------------------------------- Summary: Inappropriate payload of the @Initialized(ConversationScoped.class) event Key: CDI-354 URL: https://issues.jboss.org/browse/CDI-354 Project: CDI Specification Issues Issue Type: Bug Components: Contexts Affects Versions: 1.1.PFD Reporter: Jozef Hartinger Assignee: Pete Muir Priority: Blocker Fix For: 1.1.FD {quote} An event with qualifier @Initialized(ConversationScoped.class) is fired when the conversation context is initialized and an event with qualifier @Destroyed(ConversationScoped.class) is fired when the conversation is destroyed. The event payload is: • the conversation id if the conversation context is destroyed and is not associated with a current Servlet request, or • the ServletRequestEvent if the application is a web application deployed to a Servlet container, or • any java.lang.Object for other types of application. {quote} The conversation context is supposed to be activated in a container-provided filter with the name "CDI Conversation Filter". A Servlet Filter itself does not have access to a ServletRequestEvent instance (that is only available to ServletRequestListeners). Therefore, the implementation would either have to re-create the instance by combining ServletRequest and ServletContext or propagate the ServletRequestEvent from a ServletRequestListener. >From an application point of view, ServletRequest is the only interesting property of ServletRequestEvent anyway. Therefore, I suggest to change the wording of the spec to specify ServletRequest (or HttpServletRequest) as the payload of @Initialized(ConversationScoped.class) and @Destroyed(ConversationScoped.class) events. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-343) Bean archive types should be exclusive

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-343?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-343. --------------------------- Resolution: Done > Bean archive types should be exclusive > -------------------------------------- > > Key: CDI-343 > URL: https://issues.jboss.org/browse/CDI-343 > Project: CDI Specification Issues > Issue Type: Bug > Components: Concepts > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: 1.1.FD > > > {quote} > An explicit bean archive is an archive which contains a beans.xml file: > • with a version number of 1.1 (or later), with the bean-discovery-mode of all, or, > • with no version number, or, > • that is an empty file. > An implicit bean archive is an archive: > • which contains one or more beans with a bean defining annotation, and, > • does not contain a beans.xml with the bean-discovery-mode of none. > {quote} > A bean archive with empty beans.xml file seems to be both *explicit* and *implicit* bean archive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-341) EJB component defining annotations should be bean defining annotations

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-341?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-341. --------------------------- Resolution: Done All session beans were previously being detected, but I've made it clearer that a session bean is automatically included in an implicit bean archive. > EJB component defining annotations should be bean defining annotations > ---------------------------------------------------------------------- > > Key: CDI-341 > URL: https://issues.jboss.org/browse/CDI-341 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 1.1.PFD > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.FD > > > Forgot to put this into the PFD. RI lead has approved adding it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-342) Unify sample package names

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-342?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-342. --------------------------- Resolution: Done Done > Unify sample package names > -------------------------- > > Key: CDI-342 > URL: https://issues.jboss.org/browse/CDI-342 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.FD > > > The spec uses: > * com.acme > * org.mydomain.myapp > * org.mycompany > Using one common sample package name prefix would give the spec a cleaner feel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-347) beans_1_1.xsd is missing <if-class-not-available>

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-347?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-347. --------------------------- Resolution: Done Fixed, thanks! > beans_1_1.xsd is missing <if-class-not-available> > ------------------------------------------------- > > Key: CDI-347 > URL: https://issues.jboss.org/browse/CDI-347 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Martin Kouba > Assignee: Pete Muir > Fix For: 1.1.FD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-349) Clarify the set of interceptor bindings for a method

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-349?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-349. --------------------------- Resolution: Done Done > Clarify the set of interceptor bindings for a method > ---------------------------------------------------- > > Key: CDI-349 > URL: https://issues.jboss.org/browse/CDI-349 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Assignee: Pete Muir > Fix For: 1.1.FD > > > 9.3 "Binding an interceptor to a bean", following sentence doesn't make much sense IMHO: > {quote} > The set of interceptor bindings for a method are those declared at class level includes those declared on stereotypes. > {quote} > The Interceptors 1.2 spec, 3.3 "Binding an Interceptor to a Component", states: > {quote} > The set of interceptor bindings for a method are those declared at class level combined with those declared at method level. > {quote} > The CDI spec partially "overrides" the Interceptors spec (ommits bindings declared at method level). We should either "override" the whole sentence (and include bindings declared at method level) or reword the sentence in the CDI spec to only define stereotypes as other source of interceptor bindings. I am in favor the latter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-353) BM.createInjectionTarget() used in Unmanaged constructor

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-353?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-353. --------------------------- Resolution: Done Thanks, done. > BM.createInjectionTarget() used in Unmanaged constructor > -------------------------------------------------------- > > Key: CDI-353 > URL: https://issues.jboss.org/browse/CDI-353 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Martin Kouba > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.FD > > > This method is deprecated now - {{BeanManager.getInjectionTargetFactory()}} should be used instead. There's likely no impact on the functionality for non-contextual instances but looks inconsistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2013