November 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-452: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Assignee: John Ament > Fix For: 2.1 (Discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-ser... >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

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

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-224?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-224: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > 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 > Assignee: Antoine Sabot-Durand > Labels: F2F2016 > Fix For: 2.1 (Discussion) > > > 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 was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-157) Enabling/Disabling Extensions

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-157?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-157: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Enabling/Disabling Extensions > ----------------------------- > > Key: CDI-157 > URL: https://issues.jboss.org/browse/CDI-157 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 2.1 (Discussion) > > > Typically an extension class is packaged in a jar, along with a META-INF/services/javax.enterprise.inject.spi.Extension file which enables it. However, this means that an application, or another extension, has no way of disabling extensions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-638) Introduce a new xsd for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-638?page=com.atlassian.jira.plugin.sy... ] Work on CDI-638 started by Antoine Sabot-Durand. ------------------------------------------------ > Introduce a new xsd for CDI 2.0 > ------------------------------- > > Key: CDI-638 > URL: https://issues.jboss.org/browse/CDI-638 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Antoine Sabot-Durand > Assignee: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > CDI-420 made us to introduce the {{<trim/>}} attribute to {{beans.xml}}, so we need to introduce a new grammar ({{beans_2_0.xsd}})for CDI 2.0. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 5 months

1
0
0 / 0

Meeting on?

by John Ament

Hey guys Is today's meeting on? Looks like you guys moved your clocks ahead this past weekend, so its an hour later for me. I can still join, but have to leave at X:45. John ________________________________ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.

7 years, 5 months

4
3
0 / 0

[JBoss JIRA] (CDI-638) Introduce a new xsd for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-638?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-638: ---------------------------------------- Assignee: Antoine Sabot-Durand > Introduce a new xsd for CDI 2.0 > ------------------------------- > > Key: CDI-638 > URL: https://issues.jboss.org/browse/CDI-638 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Antoine Sabot-Durand > Assignee: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > CDI-420 made us to introduce the {{<trim/>}} attribute to {{beans.xml}}, so we need to introduce a new grammar ({{beans_2_0.xsd}})for CDI 2.0. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (CDI-643) Provide a way to easily configure injection point of an InjectionTarget

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-643?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-643: ------------------------------------------ In my remembering, this problem is for advanced CDI meta-data ({{BeanAttributesconfigurator}}, {{InjectionPointconfigurator}}, etc..). AnnotatedType is not bound to a container lifecycle, it's everywehere and usable at runtime (to create {{InjectionTarget}} for instance). > Provide a way to easily configure injection point of an InjectionTarget > ----------------------------------------------------------------------- > > Key: CDI-643 > URL: https://issues.jboss.org/browse/CDI-643 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > Creating an {{InjectionTarget}} requires an AnnotatedType. It is often convenient to create a custom {{AnnotatedType}} to add injection points in it (i.e. add {{@Inject}} on fields or methods). > We Introduced the {{AnnotatedTypeConfigurator}} helper but didn't provide a way to use it to create an {{InjectionTarget}}. > I think we should add {{BeanManager.createAnnotatedTypeConfigurator()}} to solve this and perhaps simplify other places where we could use an {{AnnotatedTypeConfigurator}} like in CDI-642 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev November 2016