September 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Created: (CDI-121) TransactionScope

by Richard Hightower (JIRA)

TransactionScope ---------------- Key: CDI-121 URL: https://issues.jboss.org/browse/CDI-121 Project: CDI Specification Issues Issue Type: Feature Request Components: Contexts Affects Versions: 1.1 (Proposed) Environment: Java EE Reporter: Richard Hightower Priority: Minor Add TransctionalScope as a standard scope to define beans whose lifecycle is the same as a given transaction. This scope should start automatically when a transaction starts (but lazily when actually needed). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

14
47
0 / 0

[JBoss JIRA] Created: (CDI-166) Disallow self consuming producers

by Martin Kouba (JIRA)

Disallow self consuming producers --------------------------------- Key: CDI-166 URL: https://issues.jboss.org/browse/CDI-166 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba Explicitly dissallow circular dependency in producers. That means bean which declares a producer and injects the result of that producer into the producer is not legal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (CDI-114) Allow registration of beans at runtime

by Vincent Massol (JIRA)

Allow registration of beans at runtime -------------------------------------- Key: CDI-114 URL: https://issues.jboss.org/browse/CDI-114 Project: CDI Specification Issues Issue Type: Feature Request Components: Beans Affects Versions: 1.0 Reporter: Vincent Massol I have use cases where I need to register a bean dynamically at runtime (see the forum reference link for a detailed description of the use case). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

8
13
0 / 0

calling 'equals' on a proxy?

by Mark Struberg

Hi Pete, others! Do you remember our discussion about what should happen if equals() gets called on a proxy? Should it route to the equals method of the currently proxied instance? LieGrue, strub

13 years, 1 month

7
18
0 / 0

@PostConstruct and @Inject methods in superclasses

by Mark Struberg

Hi! JSR-250 common annotations is pretty thin about having @PostConstruct in multiple class hierarchies. It just says that there must only be one single method annotated with @PostConstruct in a class. Thus my question: If I have public class Animal { @PostConstruct public void doInit() {..} .. } and public class Horse extends Animal { @PostConstruct public void doSomeOtherInit() {..} .. } 1.) for a contextual instance of Horse, will Animal#doInit() get executed or only the one from the 'effective' class? 2.) if 1.) was yes, then In which order do they get executed? Is this specced somewhere? 3.) Same scenario with @Inject methods. Do we specify an order? 4.) Both classes have @Inject methods and @PostConstruct. Again: which order of invocaition? Just that you understand my intention: we had a @PostConstruct method in Horse which did set a 'cached' flag in Animal. Turned out that this was a random generator depending on the intsalled server ;) LieGrue, strub

13 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (CDI-159) overly strict final check on proxyable methods

by Mark Struberg (JIRA)

overly strict final check on proxyable methods ---------------------------------------------- Key: CDI-159 URL: https://issues.jboss.org/browse/CDI-159 Project: CDI Specification Issues Issue Type: Bug Components: Interceptors Affects Versions: 1.0 Reporter: Mark Struberg Fix For: 1.1 (Proposed) CDI-1.0 currently specifies: 5.4.1. Unproxyable bean types Certain legal bean types cannot be proxied by the container: ... • classes which are declared final or have final methods, But actually this is overly strict, since this criteria should only apply to non-static and non-private methods. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

Antw.: @PostConstruct and @Inject methods in superclasses

by Arne Limburg

Hi, for @Inject there is an order specified in JSR 330. Imho we should specify that same order for @Postconstruct if we have specification for it yet. Regards, Arne ----- Reply message ----- Von: "Stuart Douglas" <stuart.w.douglas(a)gmail.com> Datum: Fr., Sep. 30, 2011 23:58 Betreff: [cdi-dev] @PostConstruct and @Inject methods in superclasses An: "Mark Struberg" <struberg(a)yahoo.de> Cc: "cdi-dev" <cdi-dev(a)lists.jboss.org> This is actually covered by the interceptors specification, from memory I am pretty sure the base class method is mean't to be called first, but the spec gives you the full order. @Inject methods are called before @PostConstuct (the are called in InjectionTarget.inject, which gets called before InjectionTarget.postConstruct). I don't think we specify an order for @Inject methods. Stuart On 01/10/2011, at 5:47 AM, Mark Struberg wrote: > Hi! > > JSR-250 common annotations is pretty thin about having @PostConstruct in multiple class hierarchies. It just says that there must only be one single method annotated with @PostConstruct in a class. Thus my question: > > If I have > > > public class Animal { > @PostConstruct > > public void doInit() {..} > .. > > } > > and > > public class Horse extends Animal { > @PostConstruct > > public void doSomeOtherInit() {..} > .. > > } > > > 1.) for a contextual instance of Horse, will Animal#doInit() get executed or only the one from the 'effective' class? > 2.) if 1.) was yes, then In which order do they get executed? Is this specced somewhere? > > 3.) Same scenario with @Inject methods. Do we specify an order? > > 4.) Both classes have @Inject methods and @PostConstruct. Again: which order of invocaition? > > > Just that you understand my intention: we had a @PostConstruct method in Horse which did set a 'cached' flag in Animal. Turned out that this was a random generator depending on the intsalled server ;) > > > LieGrue, > strub > > _______________________________________________ > cdi-dev mailing list > cdi-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/cdi-dev _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev

13 years, 2 months

1
0
0 / 0

CDI 1.1 EDR 1 draft posted

by Pete Muir

Expert group Please review this draft: http://docs.jboss.org/cdi/spec/1.1.EDR1/ http://docs.jboss.org/cdi/api/1.1.EDR1/ I would like to submit this to the JCP on Tuesday 4th October as EDR1, but to do that I want your approval :-) I am trying to stage the api jar as well as produce javadoc, but the JBoss nexus isn't cooperating :-( JBoss Nexus now syncs the cdi-api to central, so this will appear there shortly after Paul Gier beats Nexus into submission with a big enough stick ;-) I'll ping the group anyway. Pete

13 years, 2 months

6
16
0 / 0

[JBoss JIRA] Created: (CDI-171) Please enter in summary of changes from 1.0 to CDI specification 1.1

by Richard Hightower (JIRA)

Please enter in summary of changes from 1.0 to CDI specification 1.1 -------------------------------------------------------------------- Key: CDI-171 URL: https://issues.jboss.org/browse/CDI-171 Project: CDI Specification Issues Issue Type: Clarification Reporter: Richard Hightower Assignee: Pete Muir Seems this document is missing a section in the very beginning titled: changes from CDI 1.0. A lot of issues have been argued, some approved, some shot down, it would be nice to have a list of changes and perhaps a body count of things we will not add. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-146) Add support for scanning annotations

by George Gastaldi (JIRA)

Add support for scanning annotations ------------------------------------ Key: CDI-146 URL: https://issues.jboss.org/browse/CDI-146 Project: CDI Specification Issues Issue Type: Feature Request Reporter: George Gastaldi There should be a way to listen to annotations when bootstraping an extension in CDI. For example: I want to be notified whenever a @Entity is found on my deployment. With the current spec, I need to listen to every class and test if class.isAnnotationPresent(...) returns true. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2011