March 2013 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-329) @TransientReference not reflected within passivation capability validation rules for producer methods

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-329?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-329. --------------------------- Resolution: Done > @TransientReference not reflected within passivation capability validation rules for producer methods > ----------------------------------------------------------------------------------------------------- > > Key: CDI-329 > URL: https://issues.jboss.org/browse/CDI-329 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-330) BeforeBeanDiscovery.addAnnotatedType(type) should be deprecated

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-330?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-330. --------------------------- Resolution: Done > BeforeBeanDiscovery.addAnnotatedType(type) should be deprecated > --------------------------------------------------------------- > > Key: CDI-330 > URL: https://issues.jboss.org/browse/CDI-330 > Project: CDI Specification Issues > Issue Type: Bug > Components: Portable Extensions > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: 1.1.FD > > > as BeforeBeanDiscovery.addAnnotatedType(type, id) has been added which solves the problem with multiple AnnotatedTypes per Java class. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-340) Interceptor/Decorator global enablement inconsistent

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-340?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-340. --------------------------- Resolution: Done > Interceptor/Decorator global enablement inconsistent > ---------------------------------------------------- > > Key: CDI-340 > URL: https://issues.jboss.org/browse/CDI-340 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators, Interceptors > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: 1.1.FD > > > {quote} > An interceptor is said to be enabled if it is enabled in at least one bean archive *or has the @Priority annotation*. > {quote} > {quote} > A decorator is said to be enabled if it is enabled in at least one bean archive or *is listed in the final list of decorators for the > application, as defined in Section 11.5.2*. > {quote} > The latter version is more accurate since an interceptor/decorators does not necessarily need to have the @Priority annotation provided an extensions registers it globally in the AfterTypeDiscovery phase. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-339) Interceptor ordering ambiguous

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-339?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-339. --------------------------- Resolution: Done > Interceptor ordering ambiguous > ------------------------------ > > Key: CDI-339 > URL: https://issues.jboss.org/browse/CDI-339 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Interceptors > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: 1.1.FD > > > {quote} > Interceptors declared using @Interceptors, declared in ejb-jar.xml or enabled using @Priority are called before > interceptors enabled using beans.xml. > {quote} > The statement does not provide an absolute ordering of the various types of interceptor enablement but only a partial one that states that interceptors enabled using beans.xml are called last. > To make this section clear the specification should either: > a) only state the order of @Priority interceptors relatively to beans.xml interceptors (the rest can be implied from the interceptors spec), or > b) provide absolute ordering between @Interceptors, ejb-jar.xml, @Priority and beans.xml types of interceptor enablement -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-338) Decorators enabled using @Priority should be called before decorators enabled using beans.xml

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-338?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-338. --------------------------- Assignee: Pete Muir Resolution: Done > Decorators enabled using @Priority should be called before decorators enabled using beans.xml > --------------------------------------------------------------------------------------------- > > Key: CDI-338 > URL: https://issues.jboss.org/browse/CDI-338 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Pete Muir > Fix For: 1.1.FD > > > I suppose the decorators ordering should be very similar to interceptors, see 9.4 "Interceptor enablement and ordering": > {quote} > Interceptors declared using @Interceptors, declared in ejb-jar.xml or enabled using @Priority are called before interceptors enabled using beans.xml. > {quote} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-335) Incomplete exclude filters definition

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-335?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-335. --------------------------- Assignee: Pete Muir Resolution: Done > Incomplete exclude filters definition > ------------------------------------- > > Key: CDI-335 > URL: https://issues.jboss.org/browse/CDI-335 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Pete Muir > Fix For: 1.1.FD > > > 12.4 Bean discovery: > By default an exclude filter is active. If the exclude filter definition contains: > * a child element named <if-class-available> with a name attribute, and the classloader for the bean archive can load a class for that name, or > * ... > It seems there's some text missing. It should probably state the filter is not active if the definition contains <if-class-available> and the class is not available, etc. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-337) Exclude filters - typo in package matching suffix

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-337?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-337. --------------------------- Assignee: Pete Muir Resolution: Done > Exclude filters - typo in package matching suffix > ------------------------------------------------- > > Key: CDI-337 > URL: https://issues.jboss.org/browse/CDI-337 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Pete Muir > Fix For: 1.1.FD > > > {quote} > If > * the fully qualified name of the type being discovered matches the value of the name attribute of the exclude filter, or > * the package name of the type being discovered matches the value of the name attribute with a suffix ".\\*" of the exclude filter, or > * the package name of the type being discovered starts with the value of the name attribute with a suffix ".\*\\*" of the exclude filter > then we say that the type is excluded from discovery. > {quote} > ".\\*" and ".\*\\*" should be ".\*" and ".\*\*". -- 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, 8 months

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-336?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-336. --------------------------- Resolution: Done > 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 > 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, 8 months

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-336?page=com.atlassian.jira.plugin.sy... ] Pete Muir reassigned CDI-336: ----------------------------- Assignee: Pete Muir > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-340) Interceptor/Decorator global enablement inconsistent

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-340: ----------------------------------- Summary: Interceptor/Decorator global enablement inconsistent Key: CDI-340 URL: https://issues.jboss.org/browse/CDI-340 Project: CDI Specification Issues Issue Type: Clarification Components: Decorators, Interceptors Affects Versions: 1.1.PFD Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 1.1.FD {quote} An interceptor is said to be enabled if it is enabled in at least one bean archive *or has the @Priority annotation*. {quote} {quote} A decorator is said to be enabled if it is enabled in at least one bean archive or *is listed in the final list of decorators for the application, as defined in Section 11.5.2*. {quote} The latter version is more accurate since an interceptor/decorators does not necessarily need to have the @Priority annotation provided an extensions registers it globally in the AfterTypeDiscovery phase. -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2013