May 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Closed: (CDI-76) JavaDocs regarding adding scopes are weak

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-76?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-76. ------------------------ Assignee: Pete Muir Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Resolution: Done > JavaDocs regarding adding scopes are weak > ----------------------------------------- > > Key: CDI-76 > URL: https://issues.jboss.org/browse/CDI-76 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Javadoc and API, Portable Extensions > Affects Versions: 1.0 > Reporter: Lincoln Baxter III > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > JavaDocs for adding scopes via the eventing API are a bit weak. > public void addScope(@Observes final BeforeBeanDiscovery event) > { > event.addScope(ProjectScoped.class, true, false); > } > Currently it is not clear that using this method is only required when not using the @NormalScoped annotation, and that it will in fact override the annotation if present. Additional docs should probably be placed on both sides of this relationship, to that affect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-75) Clarify what happens to a bean which belongs to inactive when it observes an event

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-75?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-75. ------------------------ Assignee: Pete Muir Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Resolution: Done > Clarify what happens to a bean which belongs to inactive when it observes an event > ---------------------------------------------------------------------------------- > > Key: CDI-75 > URL: https://issues.jboss.org/browse/CDI-75 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Events > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-44) Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-44?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-44: ------------------------------ I don't think we should actually put down how they are impl'd but describe required effects. > Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation > ------------------------------------------------------------------------------------------------------------- > > Key: CDI-44 > URL: https://issues.jboss.org/browse/CDI-44 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Interceptors > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: 1.1 (Proposed) > > > When implementing interception using proxying the behaour of self invocation is quite well defined, if a method is invoked on the proxy it is intercepted, if it is invoked on the actual bean (usually through self-invocation) it is not. > When implementing interception though sub classing this is much less well definied, and the only way to track if an invocation is intercepted or not is through a thread local flag. At the moment in weld this is reset when a call is made on a client proxy, so if we have an intercepted bean A and a SessionScoped bean B and A invokes B when invokes A the second call to A is intercepted. If however B is pseudo scoped, then the second invocation is not intercepted. The correct behaviour here should be specified by the specification. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-44) Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-44?page=com.atlassian.jira.plugin.sys... ] Pete Muir reassigned CDI-44: ---------------------------- Assignee: Marius Bogoevici > Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation > ------------------------------------------------------------------------------------------------------------- > > Key: CDI-44 > URL: https://issues.jboss.org/browse/CDI-44 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Interceptors > Affects Versions: 1.0 > Reporter: Stuart Douglas > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > When implementing interception using proxying the behaour of self invocation is quite well defined, if a method is invoked on the proxy it is intercepted, if it is invoked on the actual bean (usually through self-invocation) it is not. > When implementing interception though sub classing this is much less well definied, and the only way to track if an invocation is intercepted or not is through a thread local flag. At the moment in weld this is reset when a call is made on a client proxy, so if we have an intercepted bean A and a SessionScoped bean B and A invokes B when invokes A the second call to A is intercepted. If however B is pseudo scoped, then the second invocation is not intercepted. The correct behaviour here should be specified by the specification. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-74) State explicitely that Decorators must be implemented using subclassing

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-74?page=com.atlassian.jira.plugin.sys... ] Pete Muir reassigned CDI-74: ---------------------------- Assignee: Marius Bogoevici > State explicitely that Decorators must be implemented using subclassing > ----------------------------------------------------------------------- > > Key: CDI-74 > URL: https://issues.jboss.org/browse/CDI-74 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Subclassing should be mandatory for Decorators of managed beans which are not session beans (no restrictions in the case of the latter). > This ensures that: > - fields on pseudo scoped managed beans are accessible > - there's no restriction on what kinds of constructors may a managed bean have > - no extra bean instances are created when a managed bean is created -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-74) State explicitely that Decorators must be implemented using subclassing

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-74?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-74: ------------------------------ Marius, I think we need to specify effects, not impl. Can you do this? > State explicitely that Decorators must be implemented using subclassing > ----------------------------------------------------------------------- > > Key: CDI-74 > URL: https://issues.jboss.org/browse/CDI-74 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Subclassing should be mandatory for Decorators of managed beans which are not session beans (no restrictions in the case of the latter). > This ensures that: > - fields on pseudo scoped managed beans are accessible > - there's no restriction on what kinds of constructors may a managed bean have > - no extra bean instances are created when a managed bean is created -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-70) Clarify that if an extension provides an Annotated* then it is considered "metadata complete"

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-70?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-70. ------------------------ Assignee: Pete Muir Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Resolution: Done > Clarify that if an extension provides an Annotated* then it is considered "metadata complete" > --------------------------------------------------------------------------------------------- > > Key: CDI-70 > URL: https://issues.jboss.org/browse/CDI-70 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > I think the correct behavior is to ignore any members that are missing from the AnnotatedType. You should not be directly accessing the reflection API at all. If the parameters for a method or a constructor don't match the underlying class, it should be considered a definition error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-68) Clarify that there is only one instance of a Context object per application deployment for built in contexts

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-68?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-68. ------------------------ Assignee: Pete Muir Fix Version/s: (was: 1.1 (Proposed)) Resolution: Rejected The spec already says in 6 "Associated with every scope type is a context object" clearly indicating that there is a 1-1 relationship between a scope type and a context object. The spec goes on to say that "Any instance of Context is called a context object" in 6.2 indicating there is one instance of a Context associated with a scope type. > Clarify that there is only one instance of a Context object per application deployment for built in contexts > ------------------------------------------------------------------------------------------------------------ > > Key: CDI-68 > URL: https://issues.jboss.org/browse/CDI-68 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-69) Clarify that POST_ACTIVATE and PRE_PASSIVATE on InterceptorType are only for EJBs

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-69?page=com.atlassian.jira.plugin.sys... ] Pete Muir reassigned CDI-69: ---------------------------- Assignee: Pete Muir > Clarify that POST_ACTIVATE and PRE_PASSIVATE on InterceptorType are only for EJBs > --------------------------------------------------------------------------------- > > Key: CDI-69 > URL: https://issues.jboss.org/browse/CDI-69 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-69) Clarify that POST_ACTIVATE and PRE_PASSIVATE on InterceptorType are only for EJBs

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-69?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-69. ------------------------ Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Resolution: Done > Clarify that POST_ACTIVATE and PRE_PASSIVATE on InterceptorType are only for EJBs > --------------------------------------------------------------------------------- > > Key: CDI-69 > URL: https://issues.jboss.org/browse/CDI-69 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2011