January 2017 - cdi-dev - Jboss List Archives

DeltaSpike not compiling with CDI 2.0/Weld 3

by John Ament

All, Just as a heads up, not sure if we knew this or not, but presently DeltaSpike does not compile with CDI 2 on the classpath. DS ships with a number of implementations of Annotated within. Was getAnnotations intended to be a default method? 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, 3 months

3
5
0 / 0

CDI 2.0 is (nearly) over, let's start discussion on CDI 2.1

by Antoine Sabot-Durand

Hi Guys, Release of CDI 2.0 is around the corner and I'd like to thank all of you for your help on this long adventure. Next CDI episode (or season) is also getting closer. We plan to continue our effort on CDI with a new version (probably CDI 2.1). This version try to focus on this main topic: - Java EE 8 alignment - MicroProfile enhancement - Java 9 and Jigsaw support (java 8 will always be the minimum java version support) - ... We also have a list of ticket that we postponed for CDI 2.1: https://issues.jboss.org/browse/CDI-679?filter=12328671 If you have other ideas, suggestion, wishes. Please feel free to share them here so that we can discuss their integration on the coming JSR proposal. Antoine

7 years, 3 months

4
3
0 / 0

Canceling meeting tonight

by Antoine Sabot-Durand

won't be able to attend. Sorry, Antoine

7 years, 3 months

1
0
0 / 0

Release schedule

by Antoine Sabot-Durand

Hi all, If everything goes as planned we should be able to start the official release process for CDI 2.0 next week. We still have 3 PR opens impacting only the specs doc, so I started the release of the API today to help RI and TCK to align on it. Reviews on last PRs are most welcome. Thanks to you all, Antoine

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-679) ProducerConfigurator should provide the possibility to simulate parameter injection

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-679?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-679: ------------------------------------- Fix Version/s: 2.1 (Discussion) > ProducerConfigurator should provide the possibility to simulate parameter injection > ------------------------------------------------------------------------------------ > > Key: CDI-679 > URL: https://issues.jboss.org/browse/CDI-679 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Antoine Sabot-Durand > Fix For: 2.1 (Discussion) > > > As BeanConfigurator, ProducerConfigurator should provide {{<U extends T> BeanConfigurator<U> produceWith(Function<Instance<Object>, U> callback);}} to simulate parameter injection in producer method. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-681) Spec doesn't talk about BeanConfigurator.read method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-681?page=com.atlassian.jira.plugin.sy... ] Work on CDI-681 started by Antoine Sabot-Durand. ------------------------------------------------ > Spec doesn't talk about BeanConfigurator.read method > ---------------------------------------------------- > > Key: CDI-681 > URL: https://issues.jboss.org/browse/CDI-681 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Priority: Blocker > Fix For: 2.0 .Final > > > Spec doesn't mention this method which could be confusing e.g with following (recently added) rule: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method, the Default Scope rules apply. > {quote} > When you use this {{read}} method then it makes sense to copy scope from original AnnotatedType (current Weld behaviour) so I would reword this e.g to: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method or BeanConfigurator is not initialized with one of its read methods, the Default Scope rules apply. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-681) Spec doesn't talk about BeanConfigurator.read method

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-681?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-681: ---------------------------------- I think the spec text should reference or follow the wording from the section "11.3.23. Obtaining a BeanAttributes". The important part is _"according to the rules defined in Concepts"_ which implies that the scope is defaulted. > Spec doesn't talk about BeanConfigurator.read method > ---------------------------------------------------- > > Key: CDI-681 > URL: https://issues.jboss.org/browse/CDI-681 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Priority: Blocker > Fix For: 2.0 .Final > > > Spec doesn't mention this method which could be confusing e.g with following (recently added) rule: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method, the Default Scope rules apply. > {quote} > When you use this {{read}} method then it makes sense to copy scope from original AnnotatedType (current Weld behaviour) so I would reword this e.g to: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method or BeanConfigurator is not initialized with one of its read methods, the Default Scope rules apply. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-681) Spec doesn't talk about BeanConfigurator.read method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-681?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-681: ---------------------------------------- Assignee: Antoine Sabot-Durand > Spec doesn't talk about BeanConfigurator.read method > ---------------------------------------------------- > > Key: CDI-681 > URL: https://issues.jboss.org/browse/CDI-681 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Priority: Blocker > Fix For: 2.0 .Final > > > Spec doesn't mention this method which could be confusing e.g with following (recently added) rule: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method, the Default Scope rules apply. > {quote} > When you use this {{read}} method then it makes sense to copy scope from original AnnotatedType (current Weld behaviour) so I would reword this e.g to: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method or BeanConfigurator is not initialized with one of its read methods, the Default Scope rules apply. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-681) Spec doesn't talk about BeanConfigurator.read method

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-681?page=com.atlassian.jira.plugin.sy... ] Matej Novotny edited comment on CDI-681 at 1/12/17 2:52 AM: ------------------------------------------------------------ -Also, the spec doesn't say anything about what happens when you:- * -First add a stereotype which defines a scope (like {{@Model}})- * -Then you set the scope via `scope(..)` method- EDIT: Ignore my comment, Martin is right, this is covered by 2.4.4 Default Scope chapter. was (Author: manovotn): Also, the spec doesn't say anything about what happens when you: * First add a stereotype which defines a scope (like {{@Model}}) * Then you set the scope via `scope(..)` method > Spec doesn't talk about BeanConfigurator.read method > ---------------------------------------------------- > > Key: CDI-681 > URL: https://issues.jboss.org/browse/CDI-681 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Priority: Blocker > Fix For: 2.0 .Final > > > Spec doesn't mention this method which could be confusing e.g with following (recently added) rule: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method, the Default Scope rules apply. > {quote} > When you use this {{read}} method then it makes sense to copy scope from original AnnotatedType (current Weld behaviour) so I would reword this e.g to: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method or BeanConfigurator is not initialized with one of its read methods, the Default Scope rules apply. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-681) Spec doesn't talk about BeanConfigurator.read method

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-681?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-681: ---------------------------------- A scope set manually should have precedence - see also 2.4.4. Default scope. > Spec doesn't talk about BeanConfigurator.read method > ---------------------------------------------------- > > Key: CDI-681 > URL: https://issues.jboss.org/browse/CDI-681 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Priority: Blocker > Fix For: 2.0 .Final > > > Spec doesn't mention this method which could be confusing e.g with following (recently added) rule: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method, the Default Scope rules apply. > {quote} > When you use this {{read}} method then it makes sense to copy scope from original AnnotatedType (current Weld behaviour) so I would reword this e.g to: > {quote} > If a BeanConfigurator has no scope specified via the BeanConfigurator.scope() method or BeanConfigurator is not initialized with one of its read methods, the Default Scope rules apply. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2017