Hi Ivan, In a few cases - don't recall out of my head if it is all - TomEE wraps user application in InternalApplication. IIRC it was for caching reason - TomEE not being super cleanly aligned on CDI + to avoid to get multiple instances between runtime and deployment which can break user code. Enhancing TomEE to no do it anymore or not use a wrapper when not needed can be a first step fixing that.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le ven. 8 févr. 2019 à 18:14, Ivan Junckes Filho <ivanjunc...@gmail.com> a écrit : > The @OpenAPIDefinition is not being picked up by the CDI extension because > it is only getting InternalApplication instead of picking up my custom > Application config. Any ideas why? OpenAPIDefinition configs are therefore > not showing up in the openapi doc. > > > @OpenAPIDefinition(info = > @Info( > title = "TEST", > version = "2.0", > description = "Pet Store App API", > license = @License( > name = "Apache 2.0", > url = > "http://www.apache.org/licenses/LICENSE-2.0.html";), > contact = @Contact( > name = "PetStore API Support", > url = > "https://github.com/eclipse/microprofile-open-api";, > email = "supp...@petstore.com") > ), > security = @SecurityRequirement(name = "oauth2"), > servers = @Server(url = "/test/")) > @ApplicationPath("/api") > @LoginConfig(authMethod = "MP-JWT") > public class ApplicationConfiguration extends Application { > >
