January 2017 - cdi-dev - Jboss List Archives

[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 commented on CDI-681: ----------------------------------- 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)

8 years, 2 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 edited comment on CDI-681 at 1/12/17 1:29 AM: ----------------------------------------------------------- We could also omit the _"via the BeanConfigurator.scope() method"_ part, e.g. bq. If a BeanConfigurator has no scope specified, the ... was (Author: mkouba): We can also omit the "via the BeanConfigurator.scope() method" part, e.g. bq. If a BeanConfigurator has no scope specified, the ... > 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)

8 years, 2 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: ---------------------------------- We can also omit the "via the BeanConfigurator.scope() method" part, e.g. bq. If a BeanConfigurator has no scope specified, the ... > 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)

8 years, 2 months

1
0
0 / 0

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

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-681?page=com.atlassian.jira.plugin.sy... ] Tomas Remes updated CDI-681: ---------------------------- Fix Version/s: 2.0 .Final > 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)

8 years, 2 months

1
0
0 / 0

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

by Tomas Remes (JIRA)

Tomas Remes created CDI-681: ------------------------------- Summary: 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 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)

8 years, 2 months

1
0
0 / 0

Meeting on?

by John Ament

Hi, Few of us are on IRC. Are we having the meeting today? 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.

8 years, 2 months

2
1
0 / 0

[JBoss JIRA] (CDI-680) SPI configurators - missing statement about deployment problem

by Tomas Remes (JIRA)

Tomas Remes created CDI-680: ------------------------------- Summary: SPI configurators - missing statement about deployment problem Key: CDI-680 URL: https://issues.jboss.org/browse/CDI-680 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 2.0.Beta1 Reporter: Tomas Remes In {{11.5.3. AfterBeanDiscovery event}} spec states: {quote} The second version of the method, returns a new ObserverMethodConfigurator as defined in ObserverMethodConfigurator interface to easily configure the ObserverMethod which will be added at the end of observer invocation. If the container is unable to process the configurator it automatically detects the problem and treats it as a deployment problem. {quote} I think we should add the second sentence also for other configurators (not only for {{ObserverMethodConfigurator}}) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-644) Link formatting in the specification text

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-644?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-644: ------------------------------------------ No simple solution at that moment. It's being discussed here : https://github.com/asciidoctor/asciidoctor/issues/858 Scenarios are * Switch back to docbook generation. Seems not very hard on the paper but side effects may be overkill * Write an asciidoctor post processor to add these section number. I'm not sure yet if it can be wrritten in Java or Ruby and given the priority, I'm not sure it worth it. I propose to postpone this to 2.1 > Link formatting in the specification text > ------------------------------------------ > > Key: CDI-644 > URL: https://issues.jboss.org/browse/CDI-644 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Fix For: 2.1 (Discussion) > > > In previous versions (1.x) of specification links to chapters within spec were formatted as follows: > {noformat} > Section 2.4.1, “Built-in scope types” > {noformat} > I would like to preserve this formatting (especialy the prefix "Section x.x.x") also in the new specification version because I think it's more legible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-644) Link formatting in the specification text

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-644?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-644: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 .Final) > Link formatting in the specification text > ------------------------------------------ > > Key: CDI-644 > URL: https://issues.jboss.org/browse/CDI-644 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Fix For: 2.1 (Discussion) > > > In previous versions (1.x) of specification links to chapters within spec were formatted as follows: > {noformat} > Section 2.4.1, “Built-in scope types” > {noformat} > I would like to preserve this formatting (especialy the prefix "Section x.x.x") also in the new specification version because I think it's more legible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-644) Link formatting in the specification text

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-644?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-644: ---------------------------------------- Assignee: Antoine Sabot-Durand > Link formatting in the specification text > ------------------------------------------ > > Key: CDI-644 > URL: https://issues.jboss.org/browse/CDI-644 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Assignee: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > In previous versions (1.x) of specification links to chapters within spec were formatted as follows: > {noformat} > Section 2.4.1, “Built-in scope types” > {noformat} > I would like to preserve this formatting (especialy the prefix "Section x.x.x") also in the new specification version because I think it's more legible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2017