May 2015 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-530) Specify context control and built-in context behavior in Java SE

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-530: ---------------------------------------- Summary: Specify context control and built-in context behavior in Java SE Key: CDI-530 URL: https://issues.jboss.org/browse/CDI-530 Project: CDI Specification Issues Issue Type: Feature Request Components: Java SE Integration Affects Versions: 1.2.Final Reporter: Antoine Sabot-Durand We should define how built-in context behave and provide a mean to start and stop contexts when CDI is used in Java SE -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-529) Define bean discovery rules when CDI in Java SE

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-529: ---------------------------------------- Summary: Define bean discovery rules when CDI in Java SE Key: CDI-529 URL: https://issues.jboss.org/browse/CDI-529 Project: CDI Specification Issues Issue Type: Feature Request Components: Java SE Integration Affects Versions: 1.2.Final Reporter: Antoine Sabot-Durand We should specify how bean discovery works under Java SE. Since the default {{annotated}} bean discovery mode in Java EE could lead to performance issue we need to provide a different behavior for SE. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

Bootstrap API - remove requirement for concurrent CDIs

by John D. Ament

All, I've raised a pull request to explicitly not require an implementation to support concurrent CDI instances. https://github.com/cdi-spec/cdi/pull/247 Please let me know your thoughts. I would have done it last week, but ran into some issues at the end. Sorry for the delay. In addition, I won't be able to attend next Tuesday's meeting. Please let me know if you were planning to discuss the change at the meeting. John

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-26) Bootstrap API for CDI

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-26?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand reopened CDI-26: ------------------------------------- We have overlooked an issue regarding multiple container support. http://cdi-development-mailing-list.1064426.n5.nabble.com/It-seems-we-mis.... Correction for EDR1 or enhance proposal should be done to address this point. > Bootstrap API for CDI > --------------------- > > Key: CDI-26 > URL: https://issues.jboss.org/browse/CDI-26 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment > Affects Versions: 1.0, 1.1.PFD, 1.2.Final > Reporter: Pete Muir > Assignee: John Ament > Fix For: 2.0-EDR1 > > > Weld and other CDI impls allow an embedded mode. > See http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#... for example -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-509) Upgrade to latest felix plugin in API JAR

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-509?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reopened CDI-509: -------------------------------------- Assignee: Antoine Sabot-Durand (was: John Ament) re-open to link the right PR > Upgrade to latest felix plugin in API JAR > ----------------------------------------- > > Key: CDI-509 > URL: https://issues.jboss.org/browse/CDI-509 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Javadoc and API > Affects Versions: 1.2.Final > Reporter: John Ament > Assignee: Antoine Sabot-Durand > Fix For: 2.0-EDR1 > > > Upgrade to the latest felix plugin in the API JAR to allow the API to include lambdas (version 2.5.3) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-528) Minor inconsistency in Built-in qualifiers chapter

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-528?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-528: ---------------------------------- In fact, this one: {code:java} @Any class Dog {} {code} is not required to have the additional @Default qualifier either. > Minor inconsistency in Built-in qualifiers chapter > -------------------------------------------------- > > Key: CDI-528 > URL: https://issues.jboss.org/browse/CDI-528 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Tomas Remes > Priority: Minor > > 2.3.1. Built-in qualifier types states: > {quote} > If a bean does not explicitly declare a qualifier other than @Named , the bean has exactly one additional qualifier, of type @Default . > {quote} > This means that following bean has @Named, @Default, @Any qualifiers: > {code} > @Named > public class Dog {} > {code} > but this one is not required to have @Default qualifier: > {code} > @Named > @Any > public class Dog {} > {code} > It doesn't make much sense IMHO. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

No meeting today

by Antoine Sabot-Durand

Hi all, I won’t be available for the meeting tonight. Feedback on https://github.com/cdi-spec/cdi/pull/241 <https://github.com/cdi-spec/cdi/pull/241> is always welcome. Antoine

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-528) Minor inconsistency in Built-in qualifiers chapter

by Tomas Remes (JIRA)

Tomas Remes created CDI-528: ------------------------------- Summary: Minor inconsistency in Built-in qualifiers chapter Key: CDI-528 URL: https://issues.jboss.org/browse/CDI-528 Project: CDI Specification Issues Issue Type: Clarification Reporter: Tomas Remes Priority: Minor 2.3.1. Built-in qualifier types states: {quote} If a bean does not explicitly declare a qualifier other than @Named , the bean has exactly one additional qualifier, of type @Default . {quote} This means that following bean has @Named, @Default, @Any qualifiers: {code} @Named public class Dog {} {code} but this one is not required to have @Default qualifier: {code} @Named @Any public class Dog {} {code} It doesn't make much sense IMHO. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-527) allow proxying of classes with non-private final methods

by Romain Manni-Bucau (JIRA)

[ https://issues.jboss.org/browse/CDI-527?page=com.atlassian.jira.plugin.sy... ] Romain Manni-Bucau commented on CDI-527: ---------------------------------------- @Jozef: just use a parent class with a protected final method. This is not forbidden. That said 3.2 should remove this constraint since that's a regression from 3.1. last point: why do we care about EJB at all? CDi just allow an integration with EJB but EJB shouldn't be the first model (in particular because it defines this contract definition which is not the case in CDI where internal methods are seen as well). > allow proxying of classes with non-private final methods > -------------------------------------------------------- > > Key: CDI-527 > URL: https://issues.jboss.org/browse/CDI-527 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.2.Final > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > Currently we explicitly disallow proxying of classes with non-private final methods. > EJB _does_ allow this. And there are a few final methods in the JDK and other libs. E.g. HashMap#initHashSeedAsNeeded. Currently we cannot have a producer method for it. > We might rethink our decision and allow it. Probably with an own annotation like @AllowProxying which disables this check for certain cases (subclass managed-beans or producers). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-527) allow proxying of classes with non-private final methods

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-527?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-527: ------------------------------------- I still fail to see how EJB "allows this". Can you provide a code sample of a session bean with non-private final method that is valid according to EJB 3.2? > allow proxying of classes with non-private final methods > -------------------------------------------------------- > > Key: CDI-527 > URL: https://issues.jboss.org/browse/CDI-527 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.2.Final > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > Currently we explicitly disallow proxying of classes with non-private final methods. > EJB _does_ allow this. And there are a few final methods in the JDK and other libs. E.g. HashMap#initHashSeedAsNeeded. Currently we cannot have a producer method for it. > We might rethink our decision and allow it. Probably with an own annotation like @AllowProxying which disables this check for certain cases (subclass managed-beans or producers). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2015