It seems that Arquillian Embedded Container Weld (2.0 Beta3) is not
compatible with Weld 3 Beta 1. Is this a known issue, or do we need to
bump to Weld container 3.0.x to add CDI 2.0 support?
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
So I ran into an issue after manually patching to work around WELD-2260.
It didn't work for use cases where StartMain is used to boostrap Weld. I'm
just not sure if its actually needed. E.g. the fixes for WELD-2260 may be
good enough that this isn't an issue.
Let me know what you think.
So based on the last issue I saw, I just want to run this by you guys.
I'm starting to run tests with Weld 3. I saw the following, which made me
think of the groovy issue
Caused by: java.lang.AbstractMethodError:
I just want to confirm that this is fixed on master, and its just because
Weld is a little out of date.
A customer of mine sent in a test application with the following
A war file inside ear
Two jar files inside ear/lib
One jar file inside ear/war/WEB-INF/lib
There is a class inside one of the ear/lib jar files which @Injects a bean
from the other ear/lib jar file
And there is a class inside the ear/war/WEB-INF/lib jar file that
@Specializes the bean inside an ear/lib jar file
(You can see the application at was_bugs/was_bug22 at master ·
thikade/was_bugs · GitHub )
Attempting to run this application on Weld results in an Unsatisfied
Resolution Exception. When I remove the jar containing the @Specializes
bean the application works correctly.
My first thought was that this application should not work, because the
war file and it's internal jar would have a second classloader that would
be invisible to the application classloader. However the customer
attested, and I confirmed that this application works fine on
I do not think this is an integration issue, because I tested this on
Wildfly and got the same error.
So it seems that Weld throws an Unsatisfied Resolution Exception if
@specializes exists in a class that is loaded by a classloader which is
not visible .
What do you think is the correct behaviour is in this instance? From a
classloading perspective a class inside ear/lib should not be able to see
a class inside ear/war; but on the other hand the entire purpose of a
@Specializes bean is that you drop it into your application and it
replaces the original bean. It feels appropriate that you can drop in a
war file containing the @Specializes bean and it just works without you
having to do anything extra.
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU