1 Reply Latest reply on Jan 10, 2017 1:34 PM by Gary Aitken

    webservice install issue -- no service shows up (newbie)

    Gary Aitken Newbie

      Wildfly 9.0.2

      I'm trying to port an old webservice and hit problems, so I tried a trivial one.

      It builds fine and deploys fine as an ear.

      However, when I look at it in the console, there are no web services listed;

      The ear shows up in deployments but under Deployments/demo-service.ear/subsystem/webservices I see no data or description/attributes; and under Standalone Server/Monitor:Subsystems/Subsystem:Webservices I see no endpoints.

      The log shows the app deploying and it is enabled.

      Obviously I'm doing something wrong.

      hints, anyone?

      Interface:

      @SOAPBinding (

              style=SOAPBinding.Style.DOCUMENT

      )

      public interface Demo {

              @WebMethod (operationName="getInfo")

              @WebResult (name="Info")

              public String getInfo(String requestorSecurityKey, String selectionCriteria);

      }

      Impl:

      @WebService (

              name="Demo"

      )

      @SOAPBinding (

              style=SOAPBinding.Style.DOCUMENT

      )

      public class DemoServiceImpl implements Demo {

          @WebMethod ( operationName="getInfo" )
          @WebResult (name="Info")
          public String getInfo(String requestorSecurityKey, String selectionCriteria) {
                  String xmlOutput = null;
                  xmlOutput="<DemoInfo>SomeInfo</DemoInfo>";
                  return xmlOutput;
          }

      }

        • 1. Re: webservice install issue -- no service shows up (newbie)
          Gary Aitken Newbie

          This was caused primarily by a missing META-INF/application.xml and WEB-INF/web.xml.  I was building using an ant build file rather than a maven project in an attempt to understand what was going on.  The documentation led me to believe all one had to do was annotate the code, which is incorrect; annotating only the code works only if one is using an appropriate maven environment to build and deploy.