If they are deployed ok in the server, then it's just a lookup failure of the @EJB Enricher in arquillian, which is basically just randonmly guessing if you don't specify mappedName.
Have you tried @EJB(mappedName="jndi-name") on the Injection point?
Yea, it worked out when you specify the mappedName.
Didn't think about it, because during earlier tests, Arq plainly said that he's not able to inject members.
In this case it was just throwing a NullPointerException thrown.
Yea, this changed in the CR versions. Previously each Enricher threw a Exception if they couldn't inject it's members, but multiple Enrichers may now act upon the same InjectionPoints, e.g. EJBEnricher and CDIEnricher can handle @EJB, and the order of execution is undefined.
This needs a more solid impl tho, it should know which enricher tried what and failed where, and fail it all if non of them managed.
Currently Enrichers only log on log level fine if they can't inject.
Ok, so right now there isn't any "manager" component which handles such situation (when none of the enrichers worked)?
Currently, do you have to declare which enrichers are handling which annotations, or all of the enrichers works (by default) on all annotations?
Is there an appropriate JIRA ARQ for this situations?