One test deploys the following 3 applications:

• a Service Provider, which implements an actual backend to fulfill client calls - OpenAPI annotation scan is disabled here
• a local Service Router, which routes client REST API calls to the Service Provider (via MicroProfile REST Client) - a static OpenAPI document is provided and an OASFilter implementation would modify an operation extension property to set its FQDN (local.test.district.unknown)
• another local Service Router, which routes client REST API calls to the Service Provider (via MicroProfile REST Client) - the same static OpenAPI document is provided and an OASFilter implementation would modify an operation extension property to set its FQDN (another.local.test.district.unknown)

The extension property value is set to local.test.district.unknown while there should be two different operations where it is set based on the modification that each application OASFilter instance has performed.

Another example: there 2 applications being documented at /context1 and /context2
Application 1 defines /path1 and /path2, while application 2 only defines /path1.
Given how things are documented currently, it is not clear which url to use for the service at /path2, and /context2/path2 would return a 404.