October 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-449) beans.xml examples are not valid

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-449?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-449: ------------------------------------- Fix Version/s: 2.0 .Final (was: 2.0 (discussion)) > beans.xml examples are not valid > -------------------------------- > > Key: CDI-449 > URL: https://issues.jboss.org/browse/CDI-449 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Fix For: 2.0 .Final > > > The {{beans.xml}} examples in "5.1.1. Declaring selected alternatives", "8.2.2. Decorator enablement and ordering for a bean archive" and "9.4. Interceptor enablement and ordering" (which contain a reference to beans_1_1.xsd) are not valid - {{bean-discovery-mode}} attribute is required. I think it would be appropriate to specify the version attribute as well. > The last {{beans.xml}} example in "12.4.2. Exclude filters" does not even define the reference to an XSD. Again, I believe the version and bean-discovery-mode attributes should be specified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-456) fix Bean#getBeanClass() definition

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-456?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-456: ------------------------------------- Priority: Minor (was: Major) > fix Bean#getBeanClass() definition > ---------------------------------- > > Key: CDI-456 > URL: https://issues.jboss.org/browse/CDI-456 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Reporter: Mark Struberg > Priority: Minor > Fix For: 2.1 (Discussion) > > > currently Bean#getBeanClass() is defined to return the class of the bean it produces but has one important exception: in case of a producer method or field it must return the class of the owner bean of this method or field. > Imo this only causes troubles and doesn't add any benefit. > * At the time when 'using' the Bean (create and destroy) we always ONLY need the type which is to be created. > * At the time we create interceptors we ONLY need the type which is to be created; > * At the time we create the normalscoping proxies we ONLY need the type which is to be created; > In fact the only time we need the ownerBean is when scanning the methods and fields in it. And for creating we really need the owner-Bean and not it's bean-class! > In OWB we worked around this by having our own method getReturnType() which consistently returns the type which gets created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-456) fix Bean#getBeanClass() definition

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-456?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-456: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > fix Bean#getBeanClass() definition > ---------------------------------- > > Key: CDI-456 > URL: https://issues.jboss.org/browse/CDI-456 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Reporter: Mark Struberg > Fix For: 2.1 (Discussion) > > > currently Bean#getBeanClass() is defined to return the class of the bean it produces but has one important exception: in case of a producer method or field it must return the class of the owner bean of this method or field. > Imo this only causes troubles and doesn't add any benefit. > * At the time when 'using' the Bean (create and destroy) we always ONLY need the type which is to be created. > * At the time we create interceptors we ONLY need the type which is to be created; > * At the time we create the normalscoping proxies we ONLY need the type which is to be created; > In fact the only time we need the ownerBean is when scanning the methods and fields in it. And for creating we really need the owner-Bean and not it's bean-class! > In OWB we worked around this by having our own method getReturnType() which consistently returns the type which gets created. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-461) Configuration Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-461?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand closed CDI-461. ------------------------------------ Resolution: Done No configuration feature in CDI 2.0 > Configuration Epic for CDI 2.0 > ------------------------------ > > Key: CDI-461 > URL: https://issues.jboss.org/browse/CDI-461 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (discussion) > > > This Epic ticket gathers all tickets and work document about studying the possible introduction of configuration feature in CDI 2.0. > Draft document is here : https://docs.google.com/document/d/1378aTRNgCMXRYP9LBYRuGdan0mmQ3rPjjIYLW... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-462: ------------------------------------- Fix Version/s: 2.0 (discussion) > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (discussion) > > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand closed CDI-462. ------------------------------------ > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (discussion) > > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand resolved CDI-462. -------------------------------------- Resolution: Rejected No parts in CDI 2.0 > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-462: ------------------------------------- Fix Version/s: (was: 2.0 (discussion)) > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-463) Events Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-463?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-463: ------------------------------------- Fix Version/s: 2.0 .Final (was: 2.0 (discussion)) > Events Epic for CDI 2.0 > ----------------------- > > Key: CDI-463 > URL: https://issues.jboss.org/browse/CDI-463 > Project: CDI Specification Issues > Issue Type: Epic > Components: Events > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > This Epic ticket gathers all work and documents about possible events enhancement in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1lFtgLm6hY-uECdA1r0Sfimq6vkVYThoUZsevP... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-463) Events Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-463?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand resolved CDI-463. -------------------------------------- Release Notes Text: All features done Resolution: Done > Events Epic for CDI 2.0 > ----------------------- > > Key: CDI-463 > URL: https://issues.jboss.org/browse/CDI-463 > Project: CDI Specification Issues > Issue Type: Epic > Components: Events > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (discussion) > > > This Epic ticket gathers all work and documents about possible events enhancement in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1lFtgLm6hY-uECdA1r0Sfimq6vkVYThoUZsevP... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev October 2016