Hi John! We actually don't use xbean at all in the arquillian adapter. The scanning is done manually. You can dig that in the OwbArquillianScannerService. Can you share your setup? Probably might help a bit later.
LieGrue, strub > Am 30.07.2017 um 20:23 schrieb John D. Ament <[email protected]>: > > Hi All, > > So I've been trying to dig into why OWB's CDI TCK tests are failing. I > have it down to 22 failures that should mostly be passing (or are failing > in the wrong spot). The most common failure is because of this: > > Caused by: java.lang.UnsupportedOperationException: unsupported archive > type: archive:8a164bf7-f1d7-407e-b612-633720f769f1.jar/ > at > org.apache.xbean.finder.archive.ClasspathArchive.archive(ClasspathArchive.java:87) > at > org.apache.webbeans.corespi.scanner.xbean.CdiArchive.<init>(CdiArchive.java:67) > > I'm not sure if this is an XBean issue or an OWB issue. Basically, when > bootstrapping CDI SE, we're getting some shrinkwrap JARs on the classpath > (which is on purpose, I think they're trying to make a CDI bean archive in > addition to what's in the SE container). XBean doesn't know what the > "archive" protocol means. I suspect if the first if statement in > ClasspathArchive were changed to (line > 53): if(location.getProtocol().equals("jar") || > location.getProtocol().equals("archive")) { then it would fix it, but not > 100% sure. > > John
