1 of 1 people found this helpful
ShrinkWrap Archive<?> has a merge(Archive<?> archiveToMerge) call. That's the one your looking for.
You can see it in action for instance here: http://arquillian.org/guides/functional_testing_using_drone/
However, I do not understand your use case. If you need two different WARs, just provide two methods with @Deployment annotation. Otherwise, you should be able construct single archive, which the exception of Zip/Exploded importer.
Thank you for fast reply. And yes, what I've done eariler is weird and rather newbie mistake. I am just looking for the best and most proper way of testing classes with remote interfaces and I found something like this -> https://github.com/arquillian/arquillian-showcase/tree/master/cdi-ejb/src/main/java/com/acme/cdiejb/mixedinterface and tried to adapt it to test .war instead of .ear.