I've been experiencing issues deploying a SOAP webservice implementation which class files live inside of a Wildfly Module. The module is a global module which the Web Application has access to (I know b/c it is able to access other classes stored within the module) and no deployment errors occur. However, I also never receive a log stating "Adding service endpoint metadata" as it would under normal circumstances and a wsdl is never generated.
For reference, I have 3 other SOAP webservices deployed in the same container but all of their implementation classes exist inside of a jar residing within their corresponding web application. Is their a known issue with storing the webservice implementation within a Module? For reasons I cannot disclose, this needs to not be an issue. Any help would be greatly appreciated.
Best How To :
After conversing with @federico-sierra we found the issue to be with the dependency declaration in /META-INF/MANFIEST.MF of the web application.
My original manifest file appeared as such:
Dependencies: org.webservice.impl.library, org.apache.log4j
Created-By: Apache Maven 3.2.2
Archiver-Version: Plexus Archive
When the dependency line should have contained 'annotations' next to my webservice classpath:
Dependencies: org.webservice.impl.library annotations, org.apache.log4j
Furthermore, after making this change my webservice implementation jar needed to be recompiled with the maven jandex plugin so the required jandex.idx would get generated inside of the jar. The maven plugin description is location at: https://github.com/wildfly/jandex-maven-plugin. Note: There is an ANT plugin available if needed.