JP, We have had similar challenges with our service where Axis2 (1.2) resolves to port 80 instead of a custom port where we have our services available on Jboss. One reason for that is our client goes thru apache web server in the middle and hence the port is always resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the following parameters as Charitha outlined. Did you try accessing the same services thru SOAPUI and see if it is also doing the same?. regards Madhav
Subject: RE: wsdl port address uses incorrect port number for httpsDate: Sun, 21 Sep 2008 09:51:13 -0600From: [EMAIL PROTECTED]: axis-user@ws.apache.org; axis-user@ws.apache.org Hi,My Axis2 web service is deployed for secure access and the URL is of the form "https://<hostname>/axis2/services/Version?wsdl". However when the WSDL is returned, port number 80 is specified in the soap address instead of port 443 (default port for https).I have verified that the port number in the request object is also 443. Is this a bug in Axis2?Regards,Jai-----Original Message-----From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]: Fri 9/19/2008 8:52 AMTo: [EMAIL PROTECTED]: RE: wsdl port address uses incorrect port numberHi Charitha,I am not including the wsdl with the aar file. Including the wsdlcausing other problems. (There is a separate email chain on this issue).I do want the hostname to be updated to the machine name or ip addressof the installed machine. The issue is port number is being set to awrong value. How does Axis2 determine what the port number should be setto? Is there some way we can specify what the port number should be?Regards,Jai-----Original Message-----From: charitha kankanamge [mailto:[EMAIL PROTECTED]: Friday, September 19, 2008 8:24 AMTo: [EMAIL PROTECTED]: Re: wsdl port address uses incorrect port numberHi,You may set modifyUserWsdlPortAddress parameter to false in yourservices.xml.<parameter name="*modifyUserWSDLPortAddress*">false</parameter>If you set this parameter to false and useoriginalWsdl set to true, theport address specified in the original wsdl (wsdl included in META-INFdirectory of your service archive) will be unchanged.regardsCharithahttp://charithaka.blogspot.comhttp://www.wso2.orgPugalia, Jai P (JP) wrote:> Hi,> > Looks like the wsdl port numbers being populated in the wsdl port> address by Axis2 is incorrect.> > <wsdl:service name="Version">> <wsdl:port name="VersionSOAP11port_https"> binding="ns0:VersionSOAP11Binding">> <soap:address> location="https://1.2.3.4:80/axis2/services/Version> <https://1.2.3.4:80/axis2/services/Version>" />> </wsdl:port>> <wsdl:port name="VersionSOAP11port_http1"> binding="ns0:VersionSOAP11Binding">> <soap:address> location="http://1.2.3.4:8080/axis2/services/Version> <http://1.2.3.4:8080/axis2/services/Version>" />> </wsdl:port>> </wsdl:service>> > In our situation, the port number for https should be 443 and port for> http should be 80. Is there any configuration which needs to be> modified such that the right port number is included in the wsdl when> it is retrieved using ?wsdl option.> > Thanks,> Jai> > >>----------------------------------------------------------------------->->>No virus found in this incoming message.>Checked by AVG.>Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date:>9/18/2008 5:03 PM> >---------------------------------------------------------------------To unsubscribe, e-mail: [EMAIL PROTECTED] additional commands, e-mail: [EMAIL PROTECTED] unsubscribe, e-mail: [EMAIL PROTECTED] additional commands, e-mail: [EMAIL PROTECTED] _________________________________________________________________ Stay up to date on your PC, the Web, and your mobile phone with Windows Live. http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/
