March 2013 - cdi-dev - Jboss List Archives

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

by Jozef Hartinger (JIRA)

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

12 years, 9 months

1
0
0 / 0

Decorators enabled using @Priority should be called before decorators enabled using beans.xml

by Martin Kouba

https://issues.jboss.org/browse/CDI-338 I think one sentence is missing in 8.2 "Decorator enablement and ordering"... Martin

12 years, 9 months

1
0
0 / 0

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

by Martin Kouba (JIRA)

Martin Kouba created CDI-338: -------------------------------- Summary: 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 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

12 years, 9 months

1
0
0 / 0

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

by Martin Kouba (JIRA)

Martin Kouba created CDI-337: -------------------------------- Summary: 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 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-324) Update InjectionPoint getBean() and isTransient() methods description to reflect Event instance

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-324?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-324: ---------------------------------- Ok, I accept. The part of the sentence which I thought is missing *Event* is the part about defining injection point: {quote} The getBean() method returns the Bean object representing the bean that defines the injection point. If the injection point does not belong to a bean, getBean() returns a null value. If the injection point represents a dynamically obtained *instance or event*, the getBean() method should return the Bean object representing the bean that defines *the Instance injection point*. {quote} And the same for {{isTransient()}}. Compare with {{getMember()}} description where *"...that defines the Instance or Event injection point..."* is used. > Update InjectionPoint getBean() and isTransient() methods description to reflect Event instance > ----------------------------------------------------------------------------------------------- > > Key: CDI-324 > URL: https://issues.jboss.org/browse/CDI-324 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Pete Muir > Priority: Minor > > Also update {{javax.enterprise.inject.spi.InjectionPoint}} javadoc. -- 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

12 years, 9 months

1
0
0 / 0

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

by Martin Kouba (JIRA)

Martin Kouba created CDI-336: -------------------------------- Summary: 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

12 years, 9 months

1
0
0 / 0

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

by Martin Kouba (JIRA)

Martin Kouba created CDI-335: -------------------------------- Summary: 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 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-334) Issues with global enablement of alternatives

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-334: ----------------------------------- Summary: Issues with global enablement of alternatives Key: CDI-334 URL: https://issues.jboss.org/browse/CDI-334 Project: CDI Specification Issues Issue Type: Bug Components: Beans, Resolution Affects Versions: 1.1.PFD Reporter: Jozef Hartinger Assignee: Pete Muir Fix For: 1.1.FD * Section 5.1 last paragraph does not reflect global enablement of alternatives. * Section 5.1.1 fails to define how @Priority relates to: ** alternative stereotypes ** producers * Section 5.1.6 does not reflect global enablement of alternatives Section 5.2.2: ** generally the section needs to take global enablement of alternatives into account ** "If all the beans left are alternatives with a priority, then the container will select the alternative with the highest priority, and the ambiguous dependency is called resolvable." *** there is no guarantee that there is a single alternative with the highest priority. The spec should define what happens in that case. *** also, the statement should not only consider "alternatives" but also producers defined on alternatives * Section 5.3.1 - same as 5.2.2 * Recommended priority ranges for alternatives should be defined somewhere -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-331) Instance.iterator() shouldn't include non-alternatives that haven't been replaced

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-331?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-331: -------------------------- Summary: Instance.iterator() shouldn't include non-alternatives that haven't been replaced (was: Instance.iterator() shouldn't include disabled alternatives) > Instance.iterator() shouldn't include non-alternatives that haven't been replaced > --------------------------------------------------------------------------------- > > Key: CDI-331 > URL: https://issues.jboss.org/browse/CDI-331 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Affects Versions: 1.1.PRD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: TBD > > > The specification currently says that: > {quote} > The iterator() method must: > • Identify the set of beans that have the required type and required qualifiers and are eligible for injection into the class into > which the parent Instance was injected, according to the rules of typesafe resolution, as defined in Section 5.2.1. > {quote} > The ambiguity resolution algorithm as defined in 5.2.2 should be applied. > This is explicitly required for get() but is not required for iterator(). This causes the following inconsistency: > Assume two classes Foo and Bar which both implement common interface Common. Bar is an enabled alternative. > Assume further the following > {noformat} > @Inject @Any Instance<Common> instance > {noformat} > injection point. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-324) Update InjectionPoint getBean() and isTransient() methods description to reflect Event instance

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-324?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-324. --------------------------- Fix Version/s: (was: 1.1.FD) Resolution: Rejected As per my previous comment, the spec does cover events for these two methods. > Update InjectionPoint getBean() and isTransient() methods description to reflect Event instance > ----------------------------------------------------------------------------------------------- > > Key: CDI-324 > URL: https://issues.jboss.org/browse/CDI-324 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Pete Muir > Priority: Minor > > Also update {{javax.enterprise.inject.spi.InjectionPoint}} javadoc. -- 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

12 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2013