0 Replies Latest reply on Aug 14, 2013 5:19 AM by nmay

    Web-service is always deployed with ssl endpoint on WildFly how to avoid it ?

    nmay
    nmay Aug 14, 2013 5:19 AM

      Hi,

      I update my wildfly installatoin to the latest jbossws-cxf-4.2.0.Final  webservice release.

       

      I deploy the simple username token webservice with end point address specified like this

       

      <service name="SecurityService">

          <port name="SecurityServicePort" binding="tns:SecurityServicePortBinding">

            <soap:address location="http://localhost/wsse"/>

          </port>

        </service>

       

      however wildfly  deploy it always with wsdl url like this:  http://localhost:8443/wsse?wsdl

       

      here is the log:

       

      11:12:49,539 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-14) Creating Service {http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy}SecurityService from WSDL: W

      11:12:50,408 WARNING [org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl] (MSC service thread 1-14) No assertion builder for type {http://cxf.apache.org/not/a/policy}unknownPolicy registered.

      11:12:50,431 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-14) Setting the server's publish address to be https://localhost:8443/wsse

      11:12:50,633 INFO  [org.jboss.ws.cxf.deployment] (MSC service thread 1-14) JBWS024074: WSDL published to: file:/D:/dev/tools/wildfly-8.0.0.Alpha3/standalone/data/wsdl/wsse.war/SecurityService.wsdl

      11:12:50,723 INFO  [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539: Starting service jboss.ws.endpoint."wsse.war".TestService

      11:12:50,929 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS018210: Register web context: /wsse

      11:12:50,977 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "wsse.war" (runtime-name : "wsse.war")

      11:12:50,979 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

       

       

       

      11:12:51,039 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

      11:12:51,040 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      11:12:51,040 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Alpha3 "WildFly" started ...

       

       

      Is there any way to avoid  this ?

       

      Thanks in advance !


      Regards,

      Niko