April 2013 - cdi-dev - Jboss List Archives

Fwd: Interceptors 1.2 MR candidate is available for the final review

by Pete Muir

Begin forwarded message: > From: Marina Vatkina <marina.vatkina(a)oracle.com> > Subject: Interceptors 1.2 MR candidate is available for the final review > Date: 12 April 2013 02:20:17 BST > To: jsr345-experts(a)ejb-spec.java.net, users(a)interceptors-spec.java.net > Cc: Pete Muir <pmuir(a)redhat.com> > Reply-To: marina.vatkina(a)oracle.com > > For those of you who follow the Interceptors 1.2 MR, > > I have uploaded what is hopefully the final MR candidate, to the Interceptors java.net download page: Update of 0411 with change bars. > > The latest javadoc: javadoc MR candidate > > As you all read the email titled "Issues with interceptors bound to a component lifecycle callback", you know why the Interceptors MR did not become final when it was originally planned. The exact changes for the removal of support for lifecycle callback method interceptors can be found in a diff version: Changes to revert support of lifecycle-c allback method-level interceptors. > > The current version also include some fixed typos and editorial changes to clearly list constructor-level interceptors whenever method-level interceptors are discussed (if applicable). > > Pete, please forward to the CDI EG. > > Any review comments must be submitted by the Monday (04/15) to be included. > > thanks, > -marina > > >

11 years

1
0
0 / 0

CDI API 1.1.Final staged

by Pete Muir

Please find the final API staged at https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... :-) Note I also have the tag staged in my git repo - https://github.com/pmuir/cdi/tree/1.1 and you can find the spec attached. We are still preparing the RI and TCK to submit the JCP, currently target at Friday, but perhaps sooner (still working with Oracle on this one). Pete

11 years

3
4
0 / 0

[JBoss JIRA] (CDI-213) Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-213?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-213: ------------------------------- Slip, never got feedback from Jens. > Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction > ----------------------------------------------------------------------------------------------------- > > Key: CDI-213 > URL: https://issues.jboss.org/browse/CDI-213 > Project: CDI Specification Issues > Issue Type: Tracker > Components: Events, Java EE integration > Reporter: Martin Kouba > Assignee: Pete Muir > Priority: Minor > Fix For: TBD > > > At the moment, the specification does not really specify what happens if an observer method does directly initiate, commit or rollback JTA transaction. > See *10.5. Observer notification*: "An observer method may not directly initiate, commit or rollback JTA transactions." -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-363) Revert changes to InjectionPoint that allow it to be injected in observer methods

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-363?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-363. --------------------------- Resolution: Done Thanks, fixed. > Revert changes to InjectionPoint that allow it to be injected in observer methods > --------------------------------------------------------------------------------- > > Key: CDI-363 > URL: https://issues.jboss.org/browse/CDI-363 > Project: CDI Specification Issues > Issue Type: Bug > Components: Events > Affects Versions: 1.1.PFD > Reporter: Jozef Hartinger > Assignee: Pete Muir > Priority: Blocker > Fix For: 1.1.FD > > > Now that EventMetadata made it to the spec this is now redundant. -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-213) Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-213?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-213: -------------------------- Fix Version/s: TBD (was: 1.1.FD) > Specify what happens if an observer method does directly initiate, commit or rollback JTA transaction > ----------------------------------------------------------------------------------------------------- > > Key: CDI-213 > URL: https://issues.jboss.org/browse/CDI-213 > Project: CDI Specification Issues > Issue Type: Tracker > Components: Events, Java EE integration > Reporter: Martin Kouba > Assignee: Pete Muir > Priority: Minor > Fix For: TBD > > > At the moment, the specification does not really specify what happens if an observer method does directly initiate, commit or rollback JTA transaction. > See *10.5. Observer notification*: "An observer method may not directly initiate, commit or rollback JTA transactions." -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-362) No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-362: ------------------------------- Slip > No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting > --------------------------------------------------------------------------------------------- > > Key: CDI-362 > URL: https://issues.jboss.org/browse/CDI-362 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Pete Muir > Fix For: TBD > > > E.g. > // allowed by EJB > // disallowed by CDI > @Stateful @RequestScoped > public class MyBean { > final void m() { }; > } > public class Other { > @EJB MyBean field; // PASS > @Inject MyBean field; // FAIL - unproxyable > } -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-362) No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-362: -------------------------- Fix Version/s: TBD (was: 1.1.FD) > No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting > --------------------------------------------------------------------------------------------- > > Key: CDI-362 > URL: https://issues.jboss.org/browse/CDI-362 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Pete Muir > Fix For: TBD > > > E.g. > // allowed by EJB > // disallowed by CDI > @Stateful @RequestScoped > public class MyBean { > final void m() { }; > } > public class Other { > @EJB MyBean field; // PASS > @Inject MyBean field; // FAIL - unproxyable > } -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-36) ObserverMethod.notify() does not forward qualifiers for Event

by Arne Limburg (JIRA)

[ https://issues.jboss.org/browse/CDI-36?page=com.atlassian.jira.plugin.sys... ] Arne Limburg commented on CDI-36: --------------------------------- Yes, for sure. But that's not convenient ;) > ObserverMethod.notify() does not forward qualifiers for Event > ------------------------------------------------------------- > > Key: CDI-36 > URL: https://issues.jboss.org/browse/CDI-36 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Jordan Ganoff > Assignee: Pete Muir > Fix For: 1.1.FD > > > There's currently no way to get the qualifiers for a fired event. ObserverMethod.notify() only passes the event object itself. Without the qualifiers it is difficult to bridge the gap between CDI events and some other event infrastructure (e.g. JMS). -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-36) ObserverMethod.notify() does not forward qualifiers for Event

by Arne Limburg (JIRA)

[ https://issues.jboss.org/browse/CDI-36?page=com.atlassian.jira.plugin.sys... ] Arne Limburg closed CDI-36. --------------------------- Resolution: Done Since the method in question was not added, this can be closed again. > ObserverMethod.notify() does not forward qualifiers for Event > ------------------------------------------------------------- > > Key: CDI-36 > URL: https://issues.jboss.org/browse/CDI-36 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Jordan Ganoff > Assignee: Pete Muir > Fix For: 1.1.FD > > > There's currently no way to get the qualifiers for a fired event. ObserverMethod.notify() only passes the event object itself. Without the qualifiers it is difficult to bridge the gap between CDI events and some other event infrastructure (e.g. JMS). -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-36) ObserverMethod.notify() does not forward qualifiers for Event

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-36?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-36: ------------------------------------ You can lookup and inject EventMetadata in the ObserverMethod implementation. > ObserverMethod.notify() does not forward qualifiers for Event > ------------------------------------------------------------- > > Key: CDI-36 > URL: https://issues.jboss.org/browse/CDI-36 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Jordan Ganoff > Assignee: Pete Muir > Fix For: 1.1.FD > > > There's currently no way to get the qualifiers for a fired event. ObserverMethod.notify() only passes the event object itself. Without the qualifiers it is difficult to bridge the gap between CDI events and some other event infrastructure (e.g. JMS). -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2013