March 2013 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-336) Incorrect exclude filters example

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-336?page=com.atlassian.jira.plugin.sy... ] Martin Kouba reopened CDI-336: ------------------------------ Remove exclamation mark from the name value. > Incorrect exclude filters example > --------------------------------- > > Key: CDI-336 > URL: https://issues.jboss.org/browse/CDI-336 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.FD > > > The example uses {{<if-class-available name="!javax.faces.context.FacesContext"/>}} instead of {{<if-class-not-available name="javax.faces.context.FacesContext"/>}} and also wrong XSD definition (beans_1_0.xsd). -- 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-278) Clarify scope of Stateless and Singleton EJB's

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-278?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-278: -------------------------- Fix Version/s: TBD (was: 1.1 (Proposed)) > Clarify scope of Stateless and Singleton EJB's > ---------------------------------------------- > > Key: CDI-278 > URL: https://issues.jboss.org/browse/CDI-278 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Stuart Douglas > Fix For: TBD > > > At the moment Stateless and Singleton beans are classified as @Dependent scope by default, which is not really very useful, as a lot of the rules for dependent scoped beans simple do not apply to them (they violate pretty much every rule for dependent scoped beans in 6.4). > I think we need to define a new scope for these beans, or at least clarify their behaviour when they are @Dependent scoped. -- 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-233) Specify target bean archive for bean added via AfterBeanDiscovery.addBean()

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-233: -------------------------- Fix Version/s: TBD (was: 1.1 (Proposed)) > Specify target bean archive for bean added via AfterBeanDiscovery.addBean() > --------------------------------------------------------------------------- > > Key: CDI-233 > URL: https://issues.jboss.org/browse/CDI-233 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Reporter: Martin Kouba > Labels: visibility > Fix For: TBD > > > This may have impact, provided that alternatives, interceptors or decorators are used. -- 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-345) Bean defining annotation (as currently specified) cannot be used for bean discovery

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-345?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-345: ------------------------------- I suspect we then need to back out this part of the change, and just do this for all scope types. > Bean defining annotation (as currently specified) cannot be used for bean discovery > ----------------------------------------------------------------------------------- > > Key: CDI-345 > URL: https://issues.jboss.org/browse/CDI-345 > Project: CDI Specification Issues > Issue Type: Bug > Components: Portable Extensions > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Priority: Blocker > Fix For: 1.1.FD > > > {quote}Any scope type, which *has an associated context* (as defined in Chapter 6), is a bean defining annotation{quote} > {quote}First the container must discover types. The container discovers: > • each Java class, interface or enum deployed in an explicit bean archive, and > • each Java class interface, or enum with a *bean defining annotation* in an implicit bean archive. > {quote} > The set of context cannot be enumerated until the AfterBeanDiscovery phase in which extensions register contexts. This creates a chicken-egg problem. -- 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-346) Unclear relation between bean discovery and @WithAnnotations

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-346?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-346: ------------------------------- I'll answer you quickly here, then we can sort out how to clarify in the spec. This class does NOT result in a bean definition, unless AfterTypeDiscovery.addAnnotatedType() is called with the relevant type, therefore the type should not be automatically added to the bean archive. > Unclear relation between bean discovery and @WithAnnotations > ------------------------------------------------------------ > > Key: CDI-346 > URL: https://issues.jboss.org/browse/CDI-346 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: 1.1.FD > > > {quote} > First the container must discover types. The container discovers: > • each Java class, interface or enum deployed in an explicit bean archive, and > • each Java class interface, or enum with a bean defining annotation in an implicit bean archive. > • each session bean > that is not excluded from discovery. > Then, container must create an AnnotatedType representing the type and fire an event of type ProcessAnnotatedType, > as defined in Section 11.5.6, for: > • every type discovered > • each Java class, interface or enum that must be delivered to a ProcessAnnotatedType observer, where the event parameter > is annotated with @WithAnnotations. > {quote} > Having a class > a) in an implicit bean archive > b) outside of bean archive > that does not define a bean defining annotation and the class must be delivered to a @WithAnnotation PAT observer method. > Should this class result in a bean definition (assuming it fulfils bean requirements)? > Would not it be easier to add the category of classes that must be delivered to @WithAnnotations PAT observer to the implicit bean archive definition? -- 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-346) Unclear relation between bean discovery and @WithAnnotations

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-346: ----------------------------------- Summary: Unclear relation between bean discovery and @WithAnnotations Key: CDI-346 URL: https://issues.jboss.org/browse/CDI-346 Project: CDI Specification Issues Issue Type: Bug Affects Versions: 1.1.PFD Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 1.1.FD {quote} First the container must discover types. The container discovers: • each Java class, interface or enum deployed in an explicit bean archive, and • each Java class interface, or enum with a bean defining annotation in an implicit bean archive. • each session bean that is not excluded from discovery. Then, container must create an AnnotatedType representing the type and fire an event of type ProcessAnnotatedType, as defined in Section 11.5.6, for: • every type discovered • each Java class, interface or enum that must be delivered to a ProcessAnnotatedType observer, where the event parameter is annotated with @WithAnnotations. {quote} Having a class a) in an implicit bean archive b) outside of bean archive that does not define a bean defining annotation and the class must be delivered to a @WithAnnotation PAT observer method. Should this class result in a bean definition (assuming it fulfils bean requirements)? Would not it be easier to add the category of classes that must be delivered to @WithAnnotations PAT observer to the implicit bean archive definition? -- 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-345) Bean defining annotation (as currently specified) cannot be used for bean discovery

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-345?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated CDI-345: -------------------------------- Description: {quote}Any scope type, which *has an associated context* (as defined in Chapter 6), is a bean defining annotation{quote} {quote}First the container must discover types. The container discovers: • each Java class, interface or enum deployed in an explicit bean archive, and • each Java class interface, or enum with a *bean defining annotation* in an implicit bean archive. {quote} The set of context cannot be enumerated until the AfterBeanDiscovery phase in which extensions register contexts. This creates a chicken-egg problem. was: {quote}Any scope type, which has an associated context (as defined in Chapter 6), is a bean defining annotation{quote} {quote}First the container must discover types. The container discovers: • each Java class, interface or enum deployed in an explicit bean archive, and • each Java class interface, or enum with a *bean defining annotation* in an implicit bean archive. {quote} The set of context cannot be enumerated until the AfterBeanDiscovery phase in which extensions register contexts. This creates a chicken-egg problem. > Bean defining annotation (as currently specified) cannot be used for bean discovery > ----------------------------------------------------------------------------------- > > Key: CDI-345 > URL: https://issues.jboss.org/browse/CDI-345 > Project: CDI Specification Issues > Issue Type: Bug > Components: Portable Extensions > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Priority: Blocker > Fix For: 1.1.FD > > > {quote}Any scope type, which *has an associated context* (as defined in Chapter 6), is a bean defining annotation{quote} > {quote}First the container must discover types. The container discovers: > • each Java class, interface or enum deployed in an explicit bean archive, and > • each Java class interface, or enum with a *bean defining annotation* in an implicit bean archive. > {quote} > The set of context cannot be enumerated until the AfterBeanDiscovery phase in which extensions register contexts. This creates a chicken-egg problem. -- 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-345) Bean defining annotation (as currently specified) cannot be used for bean discovery

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-345: ----------------------------------- Summary: Bean defining annotation (as currently specified) cannot be used for bean discovery Key: CDI-345 URL: https://issues.jboss.org/browse/CDI-345 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Affects Versions: 1.1.PFD Reporter: Jozef Hartinger Assignee: Pete Muir Priority: Blocker Fix For: 1.1.FD {quote}Any scope type, which has an associated context (as defined in Chapter 6), is a bean defining annotation{quote} {quote}First the container must discover types. The container discovers: • each Java class, interface or enum deployed in an explicit bean archive, and • each Java class interface, or enum with a *bean defining annotation* in an implicit bean archive. {quote} The set of context cannot be enumerated until the AfterBeanDiscovery phase in which extensions register contexts. This creates a chicken-egg problem. -- 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-344) bean-discovery-mode should be specified

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-344: ----------------------------------- Summary: bean-discovery-mode should be specified Key: CDI-344 URL: https://issues.jboss.org/browse/CDI-344 Project: CDI Specification Issues Issue Type: Bug Affects Versions: 1.1.PFD Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 1.1.FD It seems that the only complete source of information about the *bean-discovery-mode* attribute is the schema file. The specification should better explain the attribute, list and explain allowed values. -- 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 Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-343: ----------------------------------- Summary: 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2013