September 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (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: ------------------------ Fix Version/s: 1.1 (Proposed) (was: 1.1.PRD) > 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: Pete Muir > 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. 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

1
0
0 / 0

[JBoss JIRA] (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-52: ------------------------- Fix Version/s: 1.1 (Proposed) (was: 1.1.PRD) > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 1.1 (Proposed) > > -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-89) Add @Unwraps from Seam Solder

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-89?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-89: ------------------------- Assignee: Pete Muir Fix Version/s: 1.1.PRD (was: 1.1 (Proposed)) This is now covered by the pull request for CDI-139 https://github.com/jboss/cdi/pull/100 - please review! > Add @Unwraps from Seam Solder > ------------------------------ > > Key: CDI-89 > URL: https://issues.jboss.org/browse/CDI-89 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Stuart Douglas > Assignee: Pete Muir > Fix For: 1.1.PRD > > > @Unwraps allows for an essentially stateless scope for producer methods and fields. > At injection time a dependent scoped proxy is injected into the injection point. When a methods is invoked on this proxy it calls the corresponding @Unwraps methods to get the instance to invoke the method on. > Because the proxy is @Dependent scoped, the @Unwraps method can inject the corresponding InjectionPoint. -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-262) Remove description of built-in beans for Bean Validation validator and factory

by Gunnar Morling (JIRA)

Gunnar Morling created CDI-262: ---------------------------------- Summary: Remove description of built-in beans for Bean Validation validator and factory Key: CDI-262 URL: https://issues.jboss.org/browse/CDI-262 Project: CDI Specification Issues Issue Type: Bug Reporter: Gunnar Morling As discussed with Pete, the description of built-in beans for Bean Validation {{Validator(Factory)}} shall be removed from the CDI spec (section 3.7) as we'll describe this in the BV 1.1 spec. -- 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

2
4
0 / 0

[JBoss JIRA] (CDI-177) Clarify how default bean EL name and @Named qualifier with no value at injection point are related

by Martin Kouba (Created) (JIRA)

Clarify how default bean EL name and @Named qualifier with no value at injection point are related -------------------------------------------------------------------------------------------------- Key: CDI-177 URL: https://issues.jboss.org/browse/CDI-177 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba Related CDI 1.0 spec chapters: *2.5.2 Default bean EL names* *3.11 The qualifier @Named at injection points* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
12
0 / 0

IdentifiedAnnotatedType

by Pete Muir

All, We've discussed this in meetings, but I would like to get review of the actual changes to the spec. https://github.com/jboss/cdi/pull/97 Please give it a once over!

12 years

1
0
0 / 0

[JBoss JIRA] (CDI-24) Make it easier to build passivating contexts by making sure Contextual objects passed to them are serializable

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-24?page=com.atlassian.jira.plugin.sys... ] Pete Muir resolved CDI-24. -------------------------- Resolution: Done > Make it easier to build passivating contexts by making sure Contextual objects passed to them are serializable > -------------------------------------------------------------------------------------------------------------- > > Key: CDI-24 > URL: https://issues.jboss.org/browse/CDI-24 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PRD > > > OWB ensures that any Contextual impl passed to a passivating context is serializable, making it much easier to impl a custom passivating context. We should probably make this required by the spec. -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-75) Clarify what happens to a bean which belongs to inactive when it observes an event

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-75?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-75: ------------------------------ >From the CDI 1.1 EG meeting, 19th Sept {quote} Mark argued that this isn't 100% clear either way - it's arguable both ways. All agreed that it shouldn't be thrown by default. Will clarify that it isn't thrown, and possibly add a new state in which it is thrown (e.g. Reception.Strict or something somewhat less horribly named ;-) {quote} Jens, WDYT? Do you need this new state? > Clarify what happens to a bean which belongs to inactive when it observes an event > ---------------------------------------------------------------------------------- > > Key: CDI-75 > URL: https://issues.jboss.org/browse/CDI-75 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Events > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PRD > > -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-224) Support Decoration of no interface beans

by Aslak Knutsen (JIRA)

Aslak Knutsen created CDI-224: --------------------------------- Summary: Support Decoration of no interface beans Key: CDI-224 URL: https://issues.jboss.org/browse/CDI-224 Project: CDI Specification Issues Issue Type: Feature Request Components: Decorators Affects Versions: 1.0 Reporter: Aslak Knutsen According to CDI 1.0 Spec: "Decorators may be associated with any managed bean that is not itself an interceptor or decorator or with any EJB session bean." "The set of decorated types of a decorator includes all bean types of the managed bean which are Java interfaces, except for java.io.Serializable. The decorator bean class and its superclasses are not decorated types of the decorator." Both CDI and EJB support No interface beans, but for some reason Decorators only work on methods from a Interface. While Interceptors on the other hand work fine with Classes. I can see no technical reason to why Decorators should only work on Interfaces since all Proxies etc should already be in place. {code} import javax.decorator.Decorator; import javax.decorator.Delegate; import javax.enterprise.inject.Any; import javax.inject.Inject; import junit.framework.Assert; import org.jboss.arquillian.container.test.api.Deployment; import org.jboss.arquillian.junit.Arquillian; import org.jboss.shrinkwrap.api.ShrinkWrap; import org.jboss.shrinkwrap.api.spec.WebArchive; import org.jboss.shrinkwrap.impl.BeansXml; import org.junit.Test; import org.junit.runner.RunWith; @RunWith(Arquillian.class) public class DecoratesClassTestCase { @Deployment public static WebArchive create() { return ShrinkWrap.create(WebArchive.class) .addAsWebInfResource( new BeansXml().decorators(BusinessDecorator.class), "beans.xml"); } @Test public void shouldBeAbleToDecorate(BusinessObject business) throws Exception { Assert.assertEquals("Decorated Test", business.send("Test")); } @Decorator public static abstract class BusinessDecorator extends BusinessObject { @Inject @Delegate @Any private BusinessObject delegate; public String send(String msg) { return "Decorated " + delegate.send(msg); } } public static class BusinessObject { public String send(String msg) { return msg; } } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[JBoss JIRA] (CDI-89) Add @Unwraps from Seam Solder

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-89?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-89: ------------------------------ >From the CDI 1.1 EG meeting, 19th Sept {quote} Some beans want to manage their own lifecycle, and explicitly destroy an instance. We discussed adding a destroy() method to an interface which extends Context, which custom contexts need to implement in order to support removing arbitrary instances. This forms an SPI. We discussed that there should be an SPI for this, and proposed sharing a solution with CDI-139. We ran over all the possibilities we could come up with for identifying the bean to be destroyed, and discussed that either you get passed a dependent scoped instance or a proxy. In both cases, you can destroy the instance from just this info. {quote} > Add @Unwraps from Seam Solder > ------------------------------ > > Key: CDI-89 > URL: https://issues.jboss.org/browse/CDI-89 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: 1.1 (Proposed) > > > @Unwraps allows for an essentially stateless scope for producer methods and fields. > At injection time a dependent scoped proxy is injected into the injection point. When a methods is invoked on this proxy it calls the corresponding @Unwraps methods to get the instance to invoke the method on. > Because the proxy is @Dependent scoped, the @Unwraps method can inject the corresponding InjectionPoint. -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2012