JBoss Web Services
  1. JBoss Web Services
  2. JBWS-1019

Host address in wsdl/xsd import not in sync

    Details

    • Type: Bug Bug
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: jbossws-1.0.4
    • Component/s: jbossws-native
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 9 results 

      Description

      I have a problem with the port locations. The following is an excerpt of the published WSDL for WSRP:

      <wsdl:import location="http://192.168.15.4:8080/portal-wsrp/MarkupService?wsdl&resource=wsrp_v1_bindings.wsdl" namespace="urn:oasis:names:tc:wsrp:v1:bind"/>
      <wsdl:service name="WSRPService">
      <wsdl:port binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
      <soap:address location="http://telemachus.local:8080/portal-wsrp/PortletManagementService"/>
      </wsdl:port>

      Note that the WSDL location uses the IP address whereas the port location uses the Bonjour/ZeroConf name for my system instead. However, this name is not understood by systems which don't support ZeroConf

        Issue Links

          Activity

          Hide
          Thomas Diesler
          added a comment -

          That the import location is not in sync with the soap address is a bug. How to configure the soap address is described in the FAQ

          How does rewriting of the soap address in wsdl work?
          http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting

          Show
          Thomas Diesler
          added a comment - That the import location is not in sync with the soap address is a bug. How to configure the soap address is described in the FAQ How does rewriting of the soap address in wsdl work? http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQURLRewriting
          Hide
          Chris Laprun
          added a comment -

          Is it normal that there's no jboss.ws:service=ServiceEndpointManager service in jbossws14.sar/META-INF/jboss-service.xml in 1.0.1.GA?
          I'm re-writing the URL on the client with:
          <wsdl-override>http://$

          {jboss.bind.address}

          :8080/portal-wsrp/ServiceDescriptionService?wsdl</wsdl-override>

          I tried to use:
          <wsdl-override>http://192.168.15.4:8080/portal-wsrp/ServiceDescriptionService?wsdl</wsdl-override>
          but it didn't change anything.

          Note also that if the import location uses whatever address I put in my browser URL bar whereas the SOAP address constantly uses the .local name.

          Show
          Chris Laprun
          added a comment - Is it normal that there's no jboss.ws:service=ServiceEndpointManager service in jbossws14.sar/META-INF/jboss-service.xml in 1.0.1.GA? I'm re-writing the URL on the client with: <wsdl-override> http://$ {jboss.bind.address} :8080/portal-wsrp/ServiceDescriptionService?wsdl</wsdl-override> I tried to use: <wsdl-override> http://192.168.15.4:8080/portal-wsrp/ServiceDescriptionService?wsdl </wsdl-override> but it didn't change anything. Note also that if the import location uses whatever address I put in my browser URL bar whereas the SOAP address constantly uses the .local name.
          Hide
          Thomas Diesler
          added a comment -

          Have a look at jbossws.sar/META-INF/jbossws.beans/jboss-beans.xml

          <bean name="ServiceEndpointManager" class="org.jboss.ws.server.ServiceEndpointManager">
          <!--
          The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address>
          element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address.

          If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless AlwaysModifySOAPAddress is true.
          If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below.
          -->
          <property name="webServiceHost">$

          {jboss.bind.address}

          </property>
          <property name="webServiceSecurePort">8443</property>
          <property name="webServicePort">8080</property>
          <property name="alwaysModifySOAPAddress">true</property>
          ...
          </bean>

          Show
          Thomas Diesler
          added a comment - Have a look at jbossws.sar/META-INF/jbossws.beans/jboss-beans.xml <bean name="ServiceEndpointManager" class="org.jboss.ws.server.ServiceEndpointManager"> <!-- The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address> element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address. If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless AlwaysModifySOAPAddress is true. If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below. --> <property name="webServiceHost">$ {jboss.bind.address} </property> <property name="webServiceSecurePort">8443</property> <property name="webServicePort">8080</property> <property name="alwaysModifySOAPAddress">true</property> ... </bean>
          Hide
          Thomas Diesler
          added a comment -

          The changes for JBWS-1178 should fix this. Please verify and reopen in case it does not work for you.

          How can I build and install the latest?
          http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstallJBoss40xEJB3

          Show
          Thomas Diesler
          added a comment - The changes for JBWS-1178 should fix this. Please verify and reopen in case it does not work for you. How can I build and install the latest? http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstallJBoss40xEJB3
          Hide
          Alessio Soldano
          added a comment -

          Closing issues resolved in released versions

          Show
          Alessio Soldano
          added a comment - Closing issues resolved in released versions

            People

            • Assignee:
              Thomas Diesler
              Reporter:
              Thomas Diesler
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: