September 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-77: ------------------------------ Please review https://github.com/jboss/cdi/pull/109 > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PRD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-77: ------------------------- Assignee: Pete Muir Fix Version/s: 1.1.PRD (was: 1.1 (Proposed)) Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2010-April/002441.html (was: http://lists.jboss.org/pipermail/weld-dev/2010-April/002441.html) > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PRD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Pete Muir resolved CDI-82. -------------------------- Fix Version/s: (was: 1.1 (Proposed)) Resolution: Rejected Marking aas rejected as we are about as clear as we can be (this is left to the impl to sort out). > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici commented on CDI-82: ------------------------------------- OK. I think that this settles things reasonably. > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-82: ------------------------------ Say we have {code} public class MyInterceptor { @PostConstruct public void postConstruct(InvocationContext ctx) { } } {code} Then surely this class only defines a @PostConstruct *if* it is used as an interceptor class (and, of course, the inverse). The only issue comes that it would be nice if the container was able to validate that the @PostConstruct was correctly formed, but I don't think it can. This is how it's specified today: {quote} Lifecycle callback interceptor methods defined on an interceptor class have the following signature: void <METHOD>(InvocationContext) Lifecycle callback interceptor methods defined on a target class have the following signature: void <METHOD>() {quote} I don't think we can improve on this definition. Interceptors just defines the programming model. CDI defines that a class can either be a bean or an interceptor, however does not define the programming model. What we have today does not require the container to fail, so should work. Requiring the container not to fail is somewhat of an unusal thing anyway. > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici commented on CDI-82: ------------------------------------- I think that this issue can be completely taken over by the interceptors spec. However, the problems are visible only when CDI comes into play. The interceptors-spec has been written strictly with EJBs and @ManagedBeans in mind. > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-82: ------------------------------ I'm not sure that (2) is something CDI should deal with. This behavior should be dealt with interceptors. > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici commented on CDI-82: ------------------------------------- I think there are two parts to it: - clarify the situation of method signatures (which only the interceptors spec can deal with) - identify what is an interceptor and what isn't. As long as the interceptors spec allows for vanilla classes to be interceptors, and they can be managed beans as well in CDI, we have this ambiguity. One way of dealing with this is for the interceptors spec to allow for multiple lifecycle methods of the same kind, disambiguating between self-interception and external interception by method signature - i.e. (@PostConstruct x() is self, @PostConstruct(InvocationContext y) is external ). But again, this is not the interceptors spec JIRA :). > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-82: ------------------------------ I *think* this needs to be done in the interceptors spec. > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici commented on CDI-82: ------------------------------------- It's not defined as an error anywhere, but a server container can choose to either ignore the lifecycle method, or in some cases aggressively fail the deployment (to prevent cases when a faulty interceptor definition is actually deployed). The interceptors spec defines only what *is* an interceptor method, doesn't indicate what should be done when signatures are incorrect (which would automatically be in this case). > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2012