November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDI-14) Add instance() method to BeanManager

by Pete Muir (JIRA)

Add instance() method to BeanManager ------------------------------------ Key: CDI-14 URL: https://jira.jboss.org/browse/CDI-14 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Pete Muir Fix For: 1.1 Currently obtaining a contextual reference is quite a complex operation, adding a method like: Instance<Object> instance(); would make it much easier. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-13) Add ability to injection InjectionPoint into a decorator

by Pete Muir (JIRA)

Add ability to injection InjectionPoint into a decorator -------------------------------------------------------- Key: CDI-13 URL: https://jira.jboss.org/browse/CDI-13 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Pete Muir Fix For: 1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Marius Bogoevici (JIRA)

Specifically exclude methods inherited from java.lang.Object from the list of business method invocations --------------------------------------------------------------------------------------------------------- Key: CDI-12 URL: https://jira.jboss.org/browse/CDI-12 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Marius Bogoevici Priority: Optional Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations. - they are defined on the object; - will be present on the contextual reference; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

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

by Aslak Knutsen (JIRA)

cdi-api lists el-api as optional in pom, but is required by api --------------------------------------------------------------- Key: CDI-11 URL: https://jira.jboss.org/browse/CDI-11 Project: CDI Specification Issues Issue Type: Bug Affects Versions: 1.0 Reporter: Aslak Knutsen 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. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-464) Decorators are not applied to custom beans

by Stuart Douglas (JIRA)

Decorators are not applied to custom beans ------------------------------------------ Key: WELD-464 URL: https://jira.jboss.org/jira/browse/WELD-464 Project: Weld Issue Type: Bug Reporter: Stuart Douglas Beans added with AfterBeanDiscovery.addBean() do not have decorators applied -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-465) Interceptors are not applied to custom bean types

by Stuart Douglas (JIRA)

Interceptors are not applied to custom bean types ------------------------------------------------- Key: WELD-465 URL: https://jira.jboss.org/jira/browse/WELD-465 Project: Weld Issue Type: Bug Reporter: Stuart Douglas Beans added through the SPI do not have interceptors applied. Even though bean does not have a getInterceptorBindings() method, interceptors applied to stereotypes should still work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (CDI-4) Need a way to provide ordering for Event observers (@Observes)

by Lincoln Baxter III (JIRA)

Need a way to provide ordering for Event observers (@Observes) -------------------------------------------------------------- Key: CDI-4 URL: https://jira.jboss.org/browse/CDI-4 Project: CDI Specification Issues Issue Type: Feature Request Environment: All Reporter: Lincoln Baxter III There needs to be a way to specify some kind of ordering for Event observers. Understandably, this is somewhat counter-intuitive to the general concept of observing an event, but there is going to be need for this in an upcoming JBoss project. While it can be done manually, it might be nice to have a built-in API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-5) 9.5.1 Around-Invoke Interceptor example have wrong signature

by Aslak Knutsen (JIRA)

9.5.1 Around-Invoke Interceptor example have wrong signature ------------------------------------------------------------ Key: CDI-5 URL: https://jira.jboss.org/browse/CDI-5 Project: CDI Specification Issues Issue Type: Bug Components: Specification Affects Versions: 1.0 Reporter: Aslak Knutsen The Interceptor example in section 9.5.1 use a illegal method signature for Around-Invoke interceptors: @AroundInvoke public void aroundInvoke() throws Exception { ... } (void and no InvocationContex argument) Around-invoke methods have the following signature: Object <METHOD>(InvocationContext) throws Exception -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-573) Event qualifier resolution is upside down

by Pete Muir (JIRA)

Event qualifier resolution is upside down ----------------------------------------- Key: WELD-573 URL: https://jira.jboss.org/browse/WELD-573 Project: Weld Issue Type: Bug Components: Events Reporter: Pete Muir Priority: Blocker Fix For: 1.1.0.BETA1 Currently, we are checking that every qualifier on an observer method is on the event, should be that every qualifier on the event is on the observer method. See TypeSafeObserverResolver#matches() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

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

by Jozef Hartinger (JIRA)

Clarify InjectionTarget method parameters ----------------------------------------- Key: CDI-6 URL: https://jira.jboss.org/browse/CDI-6 Project: CDI Specification Issues Issue Type: Task Components: Specification Affects Versions: 1.0 Reporter: Jozef Hartinger 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. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010