October 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-373) XML schema http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd is password protected

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-373?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-373: ------------------------------------- Fix Version/s: 1.1.Final > XML schema http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd is password protected > --------------------------------------------------------------------------------- > > Key: CDI-373 > URL: https://issues.jboss.org/browse/CDI-373 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: David Konecny > Priority: Blocker > Fix For: 1.1.Final > > > Today I tried to access http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd and I was redirected to https://login.oracle.com/mysso/signon.jsp page. This used to work in the past. The same happens if I try to access the schema via http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/index.html#7 page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-557) Chapter "10.4.3. The EventMetadata interface" mentions fireAsyncEvent method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-557?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-557: ------------------------------------- Fix Version/s: 2.0-EDR2 > Chapter "10.4.3. The EventMetadata interface" mentions fireAsyncEvent method > ---------------------------------------------------------------------------- > > Key: CDI-557 > URL: https://issues.jboss.org/browse/CDI-557 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Priority: Minor > Fix For: 2.0-EDR2 > > > http://docs.jboss.org/cdi/spec/2.0.EDR1/cdi-spec.html#event_metadata > In paragraph for isAsync method there is: > {quote} > isAsync() returns true if the event was fired with fireAsync() or fireAsyncEvent() methods otherwise returns false. > {quote} > AFAIK There is no such method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-580) Allow interceptors and decorators to be applied to the return value of a producer method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-580?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-580: ------------------------------------- Sprint: Sprint 1 > Allow interceptors and decorators to be applied to the return value of a producer method > ---------------------------------------------------------------------------------------- > > Key: CDI-580 > URL: https://issues.jboss.org/browse/CDI-580 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 2.0-EDR1 > Reporter: Mark Struberg > Assignee: Antoine Sabot-Durand > Fix For: 2.0.Final > > > Currently the spec explicitly disallows to apply interceptors and decorators to contextual instances created by producer fields and producer methods. > if you add an Interceptor annotation to a producer method then only the invocation of the producermethod gets intercepted. The created Contextual Instance will remain a plain object. > We should explore ways to allow this somehow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-633) Intoroduce BeanManager.event()

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-633?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-633: ------------------------------------- Sprint: Sprint 1 > Intoroduce BeanManager.event() > ------------------------------ > > Key: CDI-633 > URL: https://issues.jboss.org/browse/CDI-633 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Fix For: 2.0 (discussion) > > > * this would allow to define the _specified type_ - the container may use the specified type to infer the parameterized type of the event types > * the method should return {{javax.enterprise.event.Event<Object>}} with no qualifiers -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

Passed: cdi-spec/cdi#65 (revert-300-CDI-626 - 29b1e30)

by Travis CI

Build Update for cdi-spec/cdi ------------------------------------- Build: #65 Status: Passed Duration: 7 minutes and 4 seconds Commit: 29b1e30 (revert-300-CDI-626) Author: Antoine Sabot-Durand Message: Revert "CDI-626 How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps?" View the changeset: https://github.com/cdi-spec/cdi/commit/29b1e30a3423 View the full build log and details: https://travis-ci.org/cdi-spec/cdi/builds/165469838 -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-580) Allow interceptors and decorators to be applied to the return value of a producer method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-580?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-580: ------------------------------------- Fix Version/s: 2.0.Final > Allow interceptors and decorators to be applied to the return value of a producer method > ---------------------------------------------------------------------------------------- > > Key: CDI-580 > URL: https://issues.jboss.org/browse/CDI-580 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 2.0-EDR1 > Reporter: Mark Struberg > Assignee: Antoine Sabot-Durand > Fix For: 2.0.Final > > > Currently the spec explicitly disallows to apply interceptors and decorators to contextual instances created by producer fields and producer methods. > if you add an Interceptor annotation to a producer method then only the invocation of the producermethod gets intercepted. The created Contextual Instance will remain a plain object. > We should explore ways to allow this somehow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-580) Allow interceptors and decorators to be applied to the return value of a producer method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-580?page=com.atlassian.jira.plugin.sy... ] Work on CDI-580 started by Antoine Sabot-Durand. ------------------------------------------------ > Allow interceptors and decorators to be applied to the return value of a producer method > ---------------------------------------------------------------------------------------- > > Key: CDI-580 > URL: https://issues.jboss.org/browse/CDI-580 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 2.0-EDR1 > Reporter: Mark Struberg > Assignee: Antoine Sabot-Durand > > Currently the spec explicitly disallows to apply interceptors and decorators to contextual instances created by producer fields and producer methods. > if you add an Interceptor annotation to a producer method then only the invocation of the producermethod gets intercepted. The created Contextual Instance will remain a plain object. > We should explore ways to allow this somehow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-580) Allow interceptors and decorators to be applied to the return value of a producer method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-580?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-580: ------------------------------------------ During F2F we designed an API allowing creation of proxys needed for Interceptors and decorators. This would allow adding them to custom bean as well. > Allow interceptors and decorators to be applied to the return value of a producer method > ---------------------------------------------------------------------------------------- > > Key: CDI-580 > URL: https://issues.jboss.org/browse/CDI-580 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 2.0-EDR1 > Reporter: Mark Struberg > > Currently the spec explicitly disallows to apply interceptors and decorators to contextual instances created by producer fields and producer methods. > if you add an Interceptor annotation to a producer method then only the invocation of the producermethod gets intercepted. The created Contextual Instance will remain a plain object. > We should explore ways to allow this somehow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-580) Allow interceptors and decorators to be applied to the return value of a producer method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-580?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-580: ---------------------------------------- Assignee: Antoine Sabot-Durand > Allow interceptors and decorators to be applied to the return value of a producer method > ---------------------------------------------------------------------------------------- > > Key: CDI-580 > URL: https://issues.jboss.org/browse/CDI-580 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 2.0-EDR1 > Reporter: Mark Struberg > Assignee: Antoine Sabot-Durand > > Currently the spec explicitly disallows to apply interceptors and decorators to contextual instances created by producer fields and producer methods. > if you add an Interceptor annotation to a producer method then only the invocation of the producermethod gets intercepted. The created Contextual Instance will remain a plain object. > We should explore ways to allow this somehow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-535) cdi instance injection ordering

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-535?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-535: ---------------------------------- [~meetoblivion] [~gastaldi] I don't think {{@Priority}} would introduce a misuse here: {quote} The Priority annotation can be applied to classes to indicate in what order the classes should be used. The effect of using the Priority annotation in any particular instance is defined by other specifications that define the use of a specific class. {quote} But as I said we would not be able to add priority to producer methods and fields. So it's -1. A new annotation might work as well. {{OrderBy}} would be mixed up with {{javax.persistence.OrderBy}}. bq. Even then, if you have multiple beans, all from the same field... How could that happen? > cdi instance injection ordering > ------------------------------- > > Key: CDI-535 > URL: https://issues.jboss.org/browse/CDI-535 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 2.0 (discussion) > Reporter: Ochieng Marembo > Priority: Optional > > We should allow ordering of bean instance injection using the {{Instance<MyBeanInterface>}} when an instance injection is used. > h3. Use case: > Developer always define a kind of chain of processor beans, which may need to run in specific order. > h3. Current scenario: > Using the Instance injection mechanism, a developer can inject multiple beans implementing the same interface and iterate of them. In order to ensure ordering, the developer could do one of the following: > #1 > {code:java} > private Iterable<MyBeanInterface> myBeans; > @Inject > void injectBeans(@Any Instance<MyBeanInterface> myBeans) { > //the create order does some kind of ordering on the beans. > this.myBeans = createOrder(myBeans); > } > {code} > #2 > This second option may be expensive if we have to order the beans everytime we execute the logic, and if this bean is applicationscoped, it wont make sense to do the ordering in the method call. > {code:java} > @Any > @Inject > private Instance<MyBeanInterface> myBeans; > public void doSomething() { > Iterable<MyBeanInterface> orderedbeans = createOrder(myBeans.select(someQualifier)); > } > {code} > h3. Our Proposal > We already have {{javax.annotation.Priority}} or any cdi specific annotation which we can add to {{MyBeanInterfaceImpl}} so that on injection of an {{Instance<MyBeanInterface>}}, all possible injection values are sorted based on the {{Priority.value()}} and if no annotation is defined, defaults to {{Priority.value = Integer.MAX_VALUE}} > {code:java} > public interface MyBeanInterface {} > @MyQualifier > @Priority(0) > public class MyFirstBean implements MyBeanInterface{ > } > @MyQualifier > @Priority(2) > public class MySecondBean implements MyBeanInterface{ > } > @ApplicationScoped > public class MyBeanProcessor { > //We expect that this injected instances shall be in order based on the @Priority annotation > @Any > @Inject > private Instance<MyBeanInterface> myBeans; > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev October 2016