May 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-126) Clarify whether it is allowable that a ctor is called more than once when a normal scoped bean is instantiated

by Pete Muir (JIRA)

Clarify whether it is allowable that a ctor is called more than once when a normal scoped bean is instantiated -------------------------------------------------------------------------------------------------------------- Key: CDI-126 URL: https://issues.jboss.org/browse/CDI-126 Project: CDI Specification Issues Issue Type: Clarification Reporter: Pete Muir -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (CDI-125) Clarify *when* initialization should occur for normal scoped beans

by Pete Muir (JIRA)

Clarify *when* initialization should occur for normal scoped beans ------------------------------------------------------------------ Key: CDI-125 URL: https://issues.jboss.org/browse/CDI-125 Project: CDI Specification Issues Issue Type: Clarification Reporter: Pete Muir Currently it may occur when the bean is injected or when a method is called on the bean. Weld takes the latter approach which has some limitations. Consider which is best and standarize on it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (CDI-128) We need a CDIInvocationContext which provides a getAnnotated

by Richard Hightower (JIRA)

We need a CDIInvocationContext which provides a getAnnotated ------------------------------------------------------------ Key: CDI-128 URL: https://issues.jboss.org/browse/CDI-128 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Richard Hightower The issues with InvocationContext is it was designed before CDI as part of EJB 3. In CDI, the meta-data will likely exist in an annotation, but it could exist in an XML file (Candi, and Seam XML Extension for CDI). For example, I am working on creating a standard interceptor for JCache 107. I can read the annotation from the getMethod of the InvocationContext, but if someone added the interception meta-data in an XML file, then it will not be available to InvocationContext.getMethod().getAnnotation(Cacheable.class). I propose we have an extension interface that extends InvocationContext called CDIInvocationContext that has a getAnnotated. This way if someone annotates in an XML file, then it is available to implementors for interceptors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
4
0 / 0

LifeCycle Event Callbacks and Interceptors

by Jens Schumann

Hi all! Recently I have noticed that OWB does not apply (class/method) interceptors to lifecycle event callback methods. I 've chatted with Mark and he referred me to the list. He tried to remember his research on this topic and made the point that class interceptors should probably be applied. However he has the feeling that pure method interceptors may not be applied for lifecycle event callback methods since those methods are no business methods. It seems that neither the CDI spec nor the interceptor spec covers the topic for all variations. After reading the interceptor spec again (chapter "Interceptors for LifeCycle Event Callbacks") I would follow Marks assertions. What do you think? Is there anything missing within the CDI spec (and OWB of course)? Jens

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (CDI-105) Provide a means for portable extensions to access beans.xml files

by Stuart Douglas (JIRA)

Provide a means for portable extensions to access beans.xml files ----------------------------------------------------------------- Key: CDI-105 URL: https://issues.jboss.org/browse/CDI-105 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Stuart Douglas There is currently no portable way for extensions to get access to beans.xml files installed in WEB-INF/lib, as CDI starts up before the ServletContext is availible. This would be useful for extensions that wish to add extra information to beans.xml in a different namespace. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
16
0 / 0

[JBoss JIRA] Closed: (CDI-41) Improve clarity of decorators

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-41?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-41. ------------------------ > Improve clarity of decorators > ----------------------------- > > Key: CDI-41 > URL: https://issues.jboss.org/browse/CDI-41 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > Remove bullet points from > "The decorator intercepts every method: > > • declared by a decorated type of the decorator > > • that is implemented by the bean class of the decorator." > they are removing clarity from the spec -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (CDI-28) Abstract methods on decorators

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-28?page=com.atlassian.jira.plugin.sys... ] Pete Muir reopened CDI-28: -------------------------- We should hold this one open for 14 days. > Abstract methods on decorators > ------------------------------ > > Key: CDI-28 > URL: https://issues.jboss.org/browse/CDI-28 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > If a method is abstract: > * if it is a method of a decorated type, it has a generated implementation that calls the delegate > * otherwise, definition error -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-12?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-12. ------------------------ > Specifically exclude methods inherited from java.lang.Object from the list of business method invocations > --------------------------------------------------------------------------------------------------------- > > Key: CDI-12 > URL: https://issues.jboss.org/browse/CDI-12 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Priority: Optional > Fix For: 1.1 (Confirmed) > > > Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations. > - they are defined on the object; > - will be present on the contextual reference; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

Proxy implementation leaks

by Christian Bauer

Started working with Weld 1.1.1 and found two issues that probably should be addressed (maybe just documented). They both look to me like leaking implementation details because proxies are used for components which are not @Singleton or @Dependent. @ApplicationScoped public class Bug { public Bug() { System.out.println("########## CONSTRUCT"); } public void foo() { System.out.println("##### FOO"); } public static void main(String[] args) { Weld weld = new Weld(); WeldContainer weldContainer = weld.initialize(); Bug bug = weldContainer.instance().select(Bug.class).get(); // Creates new instance of Bug bug.foo(); // Creates new instance of Bug!!! bug.foo(); // Uses existing instance weld.shutdown(); } } The proxy of Bug will call its superclass constructor several times during the lifecycle of the Bug component. I don't know if that is really necessary, but if it is, you can now no longer use constructors to initialize your component. This is an issue because - it's not documented that constructors of @ApplciationScoped (etc., proxied) components behave differently than @Singleton/@Dependent constructors - even if it's documented, it's questionable if that really should be the case. Taking away constructors as the primary means of initializing a component - e.g. obtaining resources such as database connections, reading config files, etc. - is a major change in the Java programming model. Users have to be strongly advised to use @PostConstruct then. The other issue I immediately found is also related to behavior of proxies and how transitive initializing/injection is implemented (not sure if this is actually specified somewhere): @ApplicationScoped public class Foo { @Inject Bar bar; } @ApplicationScoped public class Bar { @Inject Baz baz; @PostConstruct void init() { ... } } When I obtain a reference to Foo, I get a proxy of Foo with a reference to a proxy of Bar. The init() method of Bar is never called. The Baz component is never activated. This means I can't transitively initialize an application-scoped graph of components. I was trying to use CDI for wiring in a Swing application and I imagine this would be a common usecase. It should either be documented that there is a difference between @Singleton/@Dependent and proxy-implemented scopes, or unification should be considered.

12 years, 11 months

5
26
0 / 0

[JBoss JIRA] Commented: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-12?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici commented on CDI-12: ------------------------------------- https://github.com/jboss/cdi/pull/27 > Specifically exclude methods inherited from java.lang.Object from the list of business method invocations > --------------------------------------------------------------------------------------------------------- > > Key: CDI-12 > URL: https://issues.jboss.org/browse/CDI-12 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Priority: Optional > Fix For: 1.1 (Confirmed) > > > Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations. > - they are defined on the object; > - will be present on the contextual reference; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2011