[ https://issues.jboss.org/browse/WFLY-12313?page=com.atlassian.jira.plugin... ] Michael Edgar commented on WFLY-12313: -------------------------------------- [~brian.stansberry], I have been able to make some progress on this (changes will be kept update to date in [my feature/WFLY-12313-openapi on Github|https://github.com/wildfly/wildfly/compare/master...MikeEdgar:feat...]. The module code itself it working _somewhat_ using the management port (which will change before a PR) and it still needs to be cleaned up significantly. At this point I do have a few questions (please let me know if there is a better forum for these types of questions other than Jira) - * SmallRye OpenAPI requires a newer version of Jandex (2.1.1) than what is currently in WF (2.0.5). I have added the newer version to the dependency management of the parent POM, but the older version is still being used in the generated Jandex module. Any pointers where that version may be coming from? I will continue to attempt to figure this one out. * It seems as though the other MP modules have several constants defined in a {{Phase}} class that is pulled in from the Wildfly Core project. I am assuming similar upstream changes need to be made for this change as well, but please confirm. * I had to do a ton of digging/scanning to determine all of the locations where references needed to be added to the new module and its new dependent modules. Is there a more up-to-date guide than this? https://developer.jboss.org/wiki/HackingOnWildFly. * I am trying to follow the same pattern used in Thorntail for OpenAPI integration, which makes use of a servlet context listener that is added to the web archive during deployment. Is there a similar API in Wildfly that would allow adding an artifact to the archive? The APIs require knowledge of the feature/capabilities/attachment names and I'm not sure how to find them easily. -- This message was sent by Atlassian Jira (v7.13.8#713008)