Hi!
There are many ways Arquillian testing can fail. Without more details over what you want to accomplish it is quite hard to pinpoint an error.
We currently use Arquillian to test our service layer, which then uses ActiveObjects deeper down. We do not need to export these services as OSGi services. Instead Arquillian, or better the Adaptavist extension, creates a complete OSGi Bundle that behaves like a bitbucket plugin. This means, that it has to contain all production code you would like to test, as well as any dependency needed for that. Similarly to a normal plugin, Spring Scanning works as well. In your test code, you can inject all the necessary services. An odd thing there, only @Autowired has worked for us, @Inject did not to anything.
If you could provide a stripped down version of what you want to accomplish I could probably help further. Especially the static @BeforeDeployment annotated method is of interest, as it shows what classes and resources are packed into the test plugin.
Best regards!