May 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-53) Datasources defined on alternatives

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-53?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-53: ------------------------- Issue Type: Feature Request (was: Bug) Priority: Minor (was: Major) > Datasources defined on alternatives > ----------------------------------- > > Key: CDI-53 > URL: https://issues.jboss.org/browse/CDI-53 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Priority: Minor > Fix For: 1.1 (Proposed) > > > http://download.oracle.com/javaee/6/api/javax/annotation/sql/DataSourceDe... -- if this is used on an alternative class, only enable it if the alternative is enabled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-41) Improve clarity of decorators

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-41?page=com.atlassian.jira.plugin.sys... ] Pete Muir reassigned CDI-41: ---------------------------- Assignee: Marius Bogoevici > Improve clarity of decorators > ----------------------------- > > Key: CDI-41 > URL: https://issues.jboss.org/browse/CDI-41 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Remove bullet points from > "The decorator intercepts every method: > > • declared by a decorated type of the decorator > > • that is implemented by the bean class of the decorator." > they are removing clarity from the spec -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-28) Abstract methods on decorators

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-28?page=com.atlassian.jira.plugin.sys... ] Pete Muir reassigned CDI-28: ---------------------------- Assignee: Marius Bogoevici Do you want to apply Gavin's change Marius? > Abstract methods on decorators > ------------------------------ > > Key: CDI-28 > URL: https://issues.jboss.org/browse/CDI-28 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > If a method is abstract: > * if it is a method of a decorated type, it has a generated implementation that calls the delegate > * otherwise, definition error -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-11) cdi-api lists el-api as optional in pom, but is required by api

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-11?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-11. ------------------------ Assignee: Pete Muir Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Resolution: Done > cdi-api lists el-api as optional in pom, but is required by api > --------------------------------------------------------------- > > Key: CDI-11 > URL: https://issues.jboss.org/browse/CDI-11 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > ElResolver from el-api is a part of cdi-api's BeanManager interface, but the cdi-api pom lists el-api as optional. > http://repo2.maven.org/maven2/javax/enterprise/cdi-api/1.0-SP1/cdi-api-1.... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-6) Clarify InjectionTarget method parameters

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-6?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-6: ------------------------ Assignee: Marius Bogoevici Priority: Minor (was: Major) It needs to be option 1, and the offending text needs changing to allow this to happen. > Clarify InjectionTarget method parameters > ----------------------------------------- > > Key: CDI-6 > URL: https://issues.jboss.org/browse/CDI-6 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Jozef Hartinger > Assignee: Marius Bogoevici > Priority: Minor > Fix For: 1.1 (Proposed) > > > For the inject() method, the spec says: "inject() performs dependency injection upon the given object". It is not clear to me what does the "given object" refer two. if the CDI implementation uses proxies to implement interceptors and decorators, I can see two candidates for "the given object": > - the product of the produce() method including interceptors and decorators -> a proxy > - the target instance -> the object created by calling a constructor (no interception/decoration) > Arguments for the first option > - Let's have and extension that adds additional dependency injection capabilities by providing a custom InjectionTarget implementation and wrapping default InjectionTarget instances with custom ones. The custom InjectionTarget implementation does the additional DI in the inject() method and delegates to the default InjectionTarget instance to finish the injection. This implementation needs a direct access to the target instance (it cannot access field values through a proxy) > - Interceptor-like behavior - similarity to interceptors, where the InvocationContext.getTarget() returns the (non-intercepted) target instance > Arguments for the second option > - the contract of the produce() method says: "produce() calls the constructor annotated @Inject if it exists, or the constructor with no parameters otherwise, as defined in Section 5.5.1, "Injection using the bean constructor", and returns the resulting instance. If the class has inter- ceptors, produce() is responsible for building the interceptors and decorators of the instance." which means it returns an intercepted/decorated instance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-2) Interceptor bindings defined at method level should override those at the class level

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-2?page=com.atlassian.jira.plugin.syst... ] Pete Muir reassigned CDI-2: --------------------------- Assignee: Marius Bogoevici > Interceptor bindings defined at method level should override those at the class level > ------------------------------------------------------------------------------------- > > Key: CDI-2 > URL: https://issues.jboss.org/browse/CDI-2 > Project: CDI Specification Issues > Issue Type: Bug > Components: Interceptors > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec. > In section 9.5.2 of the spec: > If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-2) Interceptor bindings defined at method level should override those at the class level

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-2?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-2: ------------------------ Description: Gavin said: "We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec." In section 9.5.2 of the spec: If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error. was: We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec. In section 9.5.2 of the spec: If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error. > Interceptor bindings defined at method level should override those at the class level > ------------------------------------------------------------------------------------- > > Key: CDI-2 > URL: https://issues.jboss.org/browse/CDI-2 > Project: CDI Specification Issues > Issue Type: Bug > Components: Interceptors > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Gavin said: > "We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec." > In section 9.5.2 of the spec: > If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-40) XSD missing enable element

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-40?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-40. ------------------------ Fix Version/s: (was: 1.1 (Proposed)) Resolution: Out of Date I can't find instances of <enable> or <enabled> in the final spec, and definitely not in the 12.3 section. I also can't find any in master. > XSD missing enable element > -------------------------- > > Key: CDI-40 > URL: https://issues.jboss.org/browse/CDI-40 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Jason Porter > Assignee: Pete Muir > > Section 12.3 says there's an enable element, it's not there in the XSD. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

CDI github official repo moved

by Pete Muir

I've moved everything to https://github.com/jboss/cdi Please send pull requests against here from now on.

14 years, 10 months

1
0
0 / 0

Code Formatting Rules

by George Gastaldi

Hello, Which code formatting rules are we following on the spec ? Is there a Eclipse formatter XML avaiable for this project ? Regards, Goerge

14 years, 10 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2011