OWB handles synthetic methods already AFAIK, surely why we see this behavior


Romain Manni-Bucau
@rmannibucau |  Blog | Github | LinkedIn | Tomitriber

2015-08-27 14:18 GMT+02:00 arjan tijms <arjan.tijms@gmail.com>:
On Thu, Aug 27, 2015 at 9:17 AM, Jozef Hartinger <jharting@redhat.com> wrote:
> Agreed, this looks like a bug in Weld.

I checked on OWB too (using TomEE 7.0-snapshot), this time using the
reproducer as given here: https://github.com/payara/Payara/issues/407

And on OWB there did not seem to be any problems.

To double check I added another observer method to the test class that
should fail deployment, namely:

   public void foo(@Observes String someString, Integer thisshouldFail) {
        List<String> strList = Arrays.asList("s1", "s2", "s3");
        final int a = 0;
        final int b = 1;

        strList.forEach((s) -> { System.out.printf("%s - %d - %d -
%s\n", someString, a, b, s); });
    }

And that one indeed failed (as it should).

So it looks like this particular problem is localized to Weld.
_______________________________________________
cdi-dev mailing list
cdi-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev

Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.