March 2017 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-690) Automatically start a request context for async observer methods

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-690?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-690: --------------------------------- http://docs.jboss.org/cdi/spec/2.0-PFD/cdi-spec.html#request_context_ee - the third indent in the list. THe request context is active which basically means is automatically started IIUC. > Automatically start a request context for async observer methods > ---------------------------------------------------------------- > > Key: CDI-690 > URL: https://issues.jboss.org/browse/CDI-690 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: John Ament > > In many other places we start an implicit request context for method invocations (post constructs for instance). We should have an implicit request context for async observer methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-691) Fire initialized/destroyed for conversation and session scoped

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-691?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-691: --------------------------------- Isn't this in the EE part of the spec http://docs.jboss.org/cdi/spec/2.0-PFD/cdi-spec.html#session_context_ee ? > Fire initialized/destroyed for conversation and session scoped > -------------------------------------------------------------- > > Key: CDI-691 > URL: https://issues.jboss.org/browse/CDI-691 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: John Ament > > Section 6.7 indicates that initialized/destroyed are called for request and application scopes. need to also fire for conversation and session. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-692) isResolvable missing from 5.6.1

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-692?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-692: --------------------------------- John please use latest version of the cdi spec http://docs.jboss.org/cdi/spec/2.0-PFD/cdi-spec.html#dynamic_lookup. I know it's still not updated on the website - [~antoinesabot-durand] > isResolvable missing from 5.6.1 > ------------------------------- > > Key: CDI-692 > URL: https://issues.jboss.org/browse/CDI-692 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: John Ament > > Section 5.6.1 is missing the new isResolvable method http://docs.jboss.org/cdi/spec/2.0.Beta1/cdi-spec.html#dynamic_lookup -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-693) Introduce a Instance#ifResolved(Consumer<T>) method

by John Ament (JIRA)

John Ament created CDI-693: ------------------------------ Summary: Introduce a Instance#ifResolved(Consumer<T>) method Key: CDI-693 URL: https://issues.jboss.org/browse/CDI-693 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament in many cases, the logic around isResolvable/isUnsatisfied/isAmbiguous could be replaced by a consumer of the resolved instance. It would be good to introduce a ifResolved(Consumer<T>) method that consumes the resolved instance, not invoking the consumer if the instance was not resolvable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-692) isResolvable missing from 5.6.1

by John Ament (JIRA)

John Ament created CDI-692: ------------------------------ Summary: isResolvable missing from 5.6.1 Key: CDI-692 URL: https://issues.jboss.org/browse/CDI-692 Project: CDI Specification Issues Issue Type: Bug Reporter: John Ament Section 5.6.1 is missing the new isResolvable method http://docs.jboss.org/cdi/spec/2.0.Beta1/cdi-spec.html#dynamic_lookup -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-690) Automatically start a request context for async observer methods

by John Ament (JIRA)

John Ament created CDI-690: ------------------------------ Summary: Automatically start a request context for async observer methods Key: CDI-690 URL: https://issues.jboss.org/browse/CDI-690 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament In many other places we start an implicit request context for method invocations (post constructs for instance). We should have an implicit request context for async observer methods. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

2
1
0 / 0

[JBoss JIRA] (CDI-691) Fire initialized/destroyed for conversation and session scoped

by John Ament (JIRA)

John Ament created CDI-691: ------------------------------ Summary: Fire initialized/destroyed for conversation and session scoped Key: CDI-691 URL: https://issues.jboss.org/browse/CDI-691 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament Section 6.7 indicates that initialized/destroyed are called for request and application scopes. need to also fire for conversation and session. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-689) Typo or unclear message in 24.1.2

by John Ament (JIRA)

John Ament created CDI-689: ------------------------------ Summary: Typo or unclear message in 24.1.2 Key: CDI-689 URL: https://issues.jboss.org/browse/CDI-689 Project: CDI Specification Issues Issue Type: Feature Request Reporter: John Ament Section 24.1.2 includes the following text: {quote} When Running in Java EE, the container must extend the rules defined in Observer method invocation context and must also ensure that All kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent(). {code} The break after "that" in the first line seems weird, its not clear if its supposed to continue into the second line, or if the sentence is intended to continue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-689) Typo or unclear message in 24.1.2

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-689?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-689: --------------------------- Description: Section 24.1.2 includes the following text: {quote} When Running in Java EE, the container must extend the rules defined in Observer method invocation context and must also ensure that All kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent(). {quote} The break after "that" in the first line seems weird, its not clear if its supposed to continue into the second line, or if the sentence is intended to continue. was: Section 24.1.2 includes the following text: {quote} When Running in Java EE, the container must extend the rules defined in Observer method invocation context and must also ensure that All kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent(). {code} The break after "that" in the first line seems weird, its not clear if its supposed to continue into the second line, or if the sentence is intended to continue. > Typo or unclear message in 24.1.2 > --------------------------------- > > Key: CDI-689 > URL: https://issues.jboss.org/browse/CDI-689 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: John Ament > > Section 24.1.2 includes the following text: > {quote} > When Running in Java EE, the container must extend the rules defined in Observer method invocation context and must also ensure that > All kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent(). > {quote} > The break after "that" in the first line seems weird, its not clear if its supposed to continue into the second line, or if the sentence is intended to continue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-689) Typo or unclear message in 24.1.2

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-689?page=com.atlassian.jira.plugin.sy... ] John Ament updated CDI-689: --------------------------- Priority: Minor (was: Major) > Typo or unclear message in 24.1.2 > --------------------------------- > > Key: CDI-689 > URL: https://issues.jboss.org/browse/CDI-689 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: John Ament > Priority: Minor > > Section 24.1.2 includes the following text: > {quote} > When Running in Java EE, the container must extend the rules defined in Observer method invocation context and must also ensure that > All kinds of observers are called in the same client security context as the invocation of Event.fire() or Event.fireAsync() or BeanManager.fireEvent(). > {quote} > The break after "that" in the first line seems weird, its not clear if its supposed to continue into the second line, or if the sentence is intended to continue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2017