So, I found the following workaround for the problem: I put the actual tests in a stateless bean and add this bean to the deployment. It works, but I don't like this approach since it doubles the number of test related classes.
So, is it realy like this, that the test class behaves like a remote client of the deployed application?
You should be able to use the following to inject the no-interface view:
private YourNoInterfaceViewBean bean;
The mappedName should point to the JNDI name of the no-interface view.
I will try it after the weekend.
thanks a lot. Setting the mappedName to the portable JNDI name of the beans solved my problem. I also had a look at the source code of the EJBInjectionEnricher and saw that it only tries to guess the JDNI name of the beans.
Since the deployment is done by Arquillian it self, would it be possible to pass the meta-data of the deployment to the enricher?