[ https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607939#comment-12607939 ]
David Blevins commented on CDITCK-215: -------------------------------------- Ok, I see what you're talking about. This is cool. {code} public class Example { { // will compile Red<Foo> red = new Red<Foo>(); Color<Foo> color = red; // will not compile Circle<Foo> circle = new Circle<Foo>(); Shape<Foo> shape = circle; } public static class Foo {} public static class Color<X> {} public static class Red<X> extends Color<X> {} public static class Shape<X> {} public static class Circle<X> extends Shape<Object> {} } {code} > ProcessSessionBeanTest testProcessSessionBeanEvent count > -------------------------------------------------------- > > Key: CDITCK-215 > URL: https://issues.jboss.org/browse/CDITCK-215 > Project: CDI TCK > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.4.Final > Reporter: David Blevins > Assignee: Pete Muir > > [Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2] > Test: > org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent > Not sure if this is an issue or not, so filling this as a bug and not a > challenge. The test essentially has two observer methods and is asserting > that only one of them are called. > public void observeElephantSessionBean(@Observes > ProcessSessionBean<Elephant> event) > { > ProcessBeanObserver.elephantProcessSessionBean = event; > } > public void observeElephantBean(@Observes ProcessBean<Elephant> event) > { > ProcessBeanObserver.elephantProcessBeanCount++; > } > Specifically the test asserts that observeElephantSessionBean is called and > that observeElephantBean is not called. > Currently we call both because ProcessSessionBean is assignable to > ProcessBean and the generics are the same. > Is there a part of the spec that mandates only the most specific observer > method is called? > The only thing I can find is in 10.4 which says pretty clearly: > There may be arbitrarily many observer methods with the same event > parameter type and qualifiers. > A bean (or extension) may declare multiple observer methods. > Well I guess it's not that clear as it says essentially "this may happen" > rather than "this may happen...and when it does the behavior is...[all are > invoked || only the most specific is invoked]" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues