April 2013 - cdi-dev - Jboss List Archives

[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: --------------------------------- OK, so we have no chance to add a method to the existing SPI interfaces? And that means we are not able to receive the EventMetadate from a custom implementation of ObserverMethod? That's not good, but anyway, then this can wait for the next version of CDI. > 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, 8 months

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: ------------------------------------ ObserverMethod.notify(T event, Set<Annotation> qualifiers) was removed and no other version of the notify() method was introduced because that would break backwards compatibility with existing ObserverMethod implementations. See https://github.com/jboss/cdi/blob/master/api/src/main/java/javax/enterpri... > 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, 8 months

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 reopened CDI-36: ----------------------------- Sorry for reopening this issue so close before the start of Final Ballot, but I am afraid we introduced a major inconsistency in the API: We introduced {code} ObserverMethod.notify(T event, Set<Annotation> qualifiers) {code} with this ticket and afterwards introduced EventMetadata. So the change of this ticket MUST obviously be {code} ObserverMethod.notify(T event, EventMetadata metadata) {code} > 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, 8 months

1
0
0 / 0

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

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-363?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger reopened CDI-363: --------------------------------- The method name is getting better and better but still not perfect ;-) (getdType()) > 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, 8 months

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 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, 8 months

1
0
0 / 0

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

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-363?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-363: ------------------------------------- Plus EventMetadata should use the @since tag. > 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, 8 months

1
0
0 / 0

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

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-363?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-363: ------------------------------------- We should also make it clear that for an event fired from Event<Foo> the following applies: EventMetadata.getType() returns Foo EventMetadata.getInjectionPoint().getType() returns Event<Foo> Similarly, InjectionPoint.getQualifiers() represents the qualifiers on the injection point, not necessarily event qualifiers. > 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, 8 months

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: ------------------------------- Yes, the CDI spec could be better stating that. I'm happy to have a go at cleaning that up. > 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: 1.1.FD > > > 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, 8 months

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 Marina Vatkina (JIRA)

[ https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy... ] Marina Vatkina commented on CDI-362: ------------------------------------ [~pmuir] EJB spec is not final yet ;). Let's assume that the EJB spec will replace the "final" rule from 3.1 "All methods must not" to "Only private may". There is also a 2nd problem (though not in the subject line) - which methods constitute the "view". EJB spec says public (3.2 now has non-static added), and the CDI spec says all non-static non-private. Which gives a wrong impression to the CDI users (and some containers) if they also use (support) EJBs, but didn't read *very carefully* the EJB spec. > 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: 1.1.FD > > > 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, 8 months

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: ------------------------------- [~mvatkina] it's not, it's just that an EJB would *allow* a final protected/package-private method, and CDI wouldn't. > 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: 1.1.FD > > > 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2013