Hi Magesh, I don't know because there is no test case for JBWS-1472 AFAICS. Could you please create one that documents and tests the intended behavior. I reopend the issue. It should be possible to keep the original behaviour which allowed the address to be set in the WSDL and this address would always be returned so the three required scenarios are: - 1 - Use the hostname specified in the -beans.xml. 2 - Use the hostname already in the WSDL. 3 - Use the hostname of the calling client. On Wed, 2007-06-20 at 17:42 +0530, Magesh Kumar Bojan wrote: > > Thomas Diesler (JIRA) wrote: > > [ http://jira.jboss.com/jira/browse/JBWS-1609?page=all ] > > > > Thomas Diesler reopened JBWS-1609: > > ---------------------------------- > > > > > > The proposed solution binds concepts from the jbossws native stack to the general server config > > > > > >> Address in WSDL - Port value is -1 when server is requested with default port 80 > >> -------------------------------------------------------------------------------- > >> > >> Key: JBWS-1609 > >> URL: http://jira.jboss.com/jira/browse/JBWS-1609 > >> Project: JBoss Web Services > >> Issue Type: Bug > >> Security Level: Public(Everyone can see) > >> Components: jbossws-jaxws > >> Affects Versions: jbossws-1.2.0.SP1 > >> Environment: JBoss AS 4.0.5 running in port 80 and SSL port 443 > >> Reporter: Magesh Kumar B > >> Assigned To: Magesh Kumar B > >> Fix For: jbossws-2.0.0 > >> > >> Time Spent: 2 days, 7 hours > >> Remaining Estimate: 0 minutes > >> > >> When the server is running on default ports 80 the Webservices list and the WSDL URL shows the port as "-1" and when the SSL port 443 is used the Webservice list shows as "-1" and the WSDL URL shows as "http://jbossws.undefined.host:80" > >> > > > > > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx