[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
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
@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
[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
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
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