You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Pugalia, Jai P (JP)" <jp...@avaya.com> on 2008/09/19 16:55:59 UTC
wsdl port address uses incorrect port number
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
RE: wsdl port address uses incorrect port number for https
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Yes, I agree doesn't make sense to use the SimpleHTTPServer class for
http and https.
Looks like Axis2 uses a HTTPSListener internally if https configuration
is not available in the axis2.xml. However this class is private and not
exposed to general use.
I noticed the SSL configuration about configuring non-blocking https
transport based on SSL-NIO extensions. But to use it I need to configure
keystore and truststore.
All I am looking for is that the soap address generated in the WSDL has
either no port number or the correct port number for https.
JP
________________________________
From: Martin Gainty [mailto:mgainty@hotmail.com]
Sent: Monday, September 22, 2008 6:53 PM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number for https
doesnt make sense to use the same
org.apache.axis2.transport.http.SimpleHTTPServer
class for both http and https transport
this is the SSL configuration I see for configuring
HttpCoreNIOSSLListener in axis2.xml
<!-- the non blocking https transport based on HttpCore + SSL-NIO
extensions
<transportReceiver name="https"
class="org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener">
<parameter name="port" locked="false">9002</parameter>
<parameter name="non-blocking" locked="false">true</parameter>
<parameter name="keystore" locked="false">
<KeyStore>
<Location>identity.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
<KeyPassword>password</KeyPassword>
</KeyStore>
</parameter>
<parameter name="truststore" locked="false">
<TrustStore>
<Location>trust.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
</TrustStore>
</parameter>-->
<!--<parameter name="SSLVerifyClient">require</parameter>
supports optional|require or defaults to none -->
<!--</transportReceiver>-->
//the default behaviour is to have your service engage Rampart module
as in this definition in services.xml
<service...
<module ref="rampart" />
<parameter name="InflowSecurity">
<action>
<items>Timestamp Signature</items>
<signaturePropFile>service.properties</signaturePropFile>
</action>
</parameter>
<parameter name="OutflowSecurity">
<action>
<items>Timestamp Signature</items>
<user>service</user>
<passwordCallbackClass>org.apache.rampart.samples.sample04.PWCBHandler</
passwordCallbackClass>
<signaturePropFile>service.properties</signaturePropFile>
<signatureKeyIdentifier>DirectReference</signatureKeyIdentifier>
</action>
</parameter>
..
</service>
HTH
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission.
________________________________
Subject: RE: wsdl port address uses incorrect port number for https
Date: Mon, 22 Sep 2008 17:10:22 -0600
From: jpugalia@avaya.com
To: axis-user@ws.apache.org
Hi,
The proxyPort does not help us as we are not using Apache as a proxy
server.
If I configure the axis2.xml as below:
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8080</parameter>
</transportReceiver>
<transportReceiver name="https"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8443</parameter>
</transportReceiver>
then the soap address for http includes the port 8080 and the soap
address for https includes the port 8443 but the soap address itself is
http and not https.
When should the class for transportReceiver be set to for https?
If I do not specify the transportReceiver for https in axis2.xml, the
the default value of the port is taken as 80 instead of 443 which is the
default port for https.
Thanks,
JP
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https
It should be specified in the http transport listener of the axis2.xml.
You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]
Look for the following.
<!--
Uncomment the following to enable Apache2 mod_proxy. The port on
the Apache server is 80
in this case.
-->
<!--<parameter name="proxyPort">80</parameter>-->
Thanks,
Keith.
[1] http://wso2.org/projects/mashup
On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<jp...@avaya.com> wrote:
Hi Keith,
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
Thanks,
Jai
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for
https
Hi,
When its going through Apache you can use the following
parameter in the transport listener to set the port address,
<parameter name="proxyPort">80</parameter>
For the https listener you can set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<em...@hotmail.com> wrote:
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 https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: jpugalia@avaya.com
To: 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:// <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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port
number
Hi Charitha,
I am not including the wsdl with the aar file. Including
the wsdl
causing 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 address
of the installed machine. The issue is port number is
being set to a
wrong value. How does Axis2 determine what the port
number should be set
to? Is there some way we can specify what the port
number should be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port
number
Hi,
You may set modifyUserWsdlPortAddress parameter to false
in your
services.xml.
<parameter
name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl
set to true, the
port address specified in the original wsdl (wsdl
included in META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com
<http://charithaka.blogspot.com/>
http://www.wso2.org <http://www.wso2.org/>
Pugalia, 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:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
________________________________
Stay up to date on your PC, the Web, and your mobile
phone with Windows Live. See Now
<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
________________________________
Get more out of the Web. Learn 10 hidden secrets of Windows Live. Learn
Now
<http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-c
ns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_getmore_092008>
RE: wsdl port address uses incorrect port number for https
Posted by Martin Gainty <mg...@hotmail.com>.
doesnt make sense to use the same org.apache.axis2.transport.http.SimpleHTTPServer
class for both http and https transport
this is the SSL configuration I see for configuring HttpCoreNIOSSLListener in axis2.xml
<!-- the non blocking https transport based on HttpCore + SSL-NIO extensions
<transportReceiver name="https" class="org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener">
<parameter name="port" locked="false">9002</parameter>
<parameter name="non-blocking" locked="false">true</parameter>
<parameter name="keystore" locked="false">
<KeyStore>
<Location>identity.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
<KeyPassword>password</KeyPassword>
</KeyStore>
</parameter>
<parameter name="truststore" locked="false">
<TrustStore>
<Location>trust.jks</Location>
<Type>JKS</Type>
<Password>password</Password>
</TrustStore>
</parameter>-->
<!--<parameter name="SSLVerifyClient">require</parameter>
supports optional|require or defaults to none -->
<!--</transportReceiver>-->
//the default behaviour is to have your service engage Rampart module as in this definition in services.xml
<service...
<module ref="rampart" />
<parameter name="InflowSecurity">
<action>
<items>Timestamp Signature</items>
<signaturePropFile>service.properties</signaturePropFile>
</action>
</parameter>
<parameter name="OutflowSecurity">
<action>
<items>Timestamp Signature</items>
<user>service</user>
<passwordCallbackClass>org.apache.rampart.samples.sample04.PWCBHandler</passwordCallbackClass>
<signaturePropFile>service.properties</signaturePropFile>
<signatureKeyIdentifier>DirectReference</signatureKeyIdentifier>
</action>
</parameter>
..
</service>
HTH
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.
Subject: RE: wsdl port address uses incorrect port number for https
Date: Mon, 22 Sep 2008 17:10:22 -0600
From: jpugalia@avaya.com
To: axis-user@ws.apache.org
Hi,
The proxyPort does not help us as we are not using Apache
as a proxy server.
If I configure the axis2.xml as below:
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8080</parameter>
</transportReceiver>
<transportReceiver name="https"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8443</parameter>
</transportReceiver>
then the soap address for
http includes the port 8080 and the soap address for https includes the port
8443 but the soap address itself is http and not https.
When should the class for
transportReceiver be set to for https?
If I do not specify the
transportReceiver for https in axis2.xml, the the default value of the port is
taken as 80 instead of 443 which is the default port for https.
Thanks,
JP
From: keith chapman
[mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008
9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port
address uses incorrect port number for https
It should be specified in the http transport listener of the
axis2.xml. You can have a look at https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xml
for an example usage. This is the axis2.xml used in the WSO2 Mashup Server
[1]
Look for the following.
<!--
Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80
in this case.
-->
<!--<parameter name="proxyPort">80</parameter>-->
Thanks,
Keith.
[1] http://wso2.org/projects/mashup
On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<jp...@avaya.com> wrote:
Hi
Keith,
Where do I
specify this parameter? I am guessing axis2.xml. In axis2.xml, the http
transport receiver has a port parameter is set to 8080 and the https
transport receiver is commented out in axis2.xml. Am I heading in the
right direction?
Thanks,
Jai
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September
21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl
port address uses incorrect port number for https
Hi,
When its going through Apache you can use the
following parameter in the transport listener to set the port
address,
<parameter
name="proxyPort">80</parameter>
For the https listener you can
set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M
Naidu <em...@hotmail.com> wrote:
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
https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: jpugalia@avaya.com
To:
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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52
AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address
uses incorrect port number
Hi Charitha,
I am not including the
wsdl with the aar file. Including the wsdl
causing 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 address
of the installed machine.
The issue is port number is being set to a
wrong value. How does Axis2
determine what the port number should be set
to? Is there some way we can
specify what the port number should
be?
Regards,
Jai
-----Original Message-----
From:
charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19,
2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address
uses incorrect port number
Hi,
You may set
modifyUserWsdlPortAddress parameter to false in
your
services.xml.
<parameter
name="*modifyUserWSDLPortAddress*">false</parameter>
If you
set this parameter to false and useoriginalWsdl set to true, the
port
address specified in the original wsdl (wsdl included in
META-INF
directory of your service archive) will be
unchanged.
regards
Charitha
http://charithaka.blogspot.com
http://www.wso2.org
Pugalia, 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: axis-user-unsubscribe@ws.apache.org
For additional
commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To
unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional
commands, e-mail: axis-user-help@ws.apache.org
Stay up to date on your PC, the Web, and your mobile phone with Windows
Live. See Now
--
Keith Chapman
Senior Software
Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Keith Chapman
Senior Software Engineer
WSO2
Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
_________________________________________________________________
Get more out of the Web. Learn 10 hidden secrets of Windows Live.
http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008
Re: wsdl port address uses incorrect port number for https
Posted by keith chapman <ke...@gmail.com>.
Would you mind opening a JIRA issue please. That way it will be tracked.
Thanks,
Keith.
On Thu, Sep 25, 2008 at 7:34 AM, Pugalia, Jai P (JP) <jp...@avaya.com>wrote:
> Hi Keith,
>
> For now, I had solved the problem by writing my own Listener by
> implementing the TransportListener class. I like your suggestion of
> extending the existing Listener so I am going to try it out.
>
> I also tried by adding the proxyPort to the Connector configuration in the
> server.xml of Tomcat, however looks like Axis2 does not use it and instead
> takes a value of 80. I hope this gets fixed in future versions of Axis2.
>
> Thanks,
> JP
>
> ------------------------------
> *From:* keith chapman [mailto:keithgchapman@gmail.com]
> *Sent:* Wednesday, September 24, 2008 6:53 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: wsdl port address uses incorrect port number for https
>
> You could easily extend the Listener shipped with Axis2 and override its
> getEPRsForService method. This is the method that generates the endpoint
> address, so you could handle it the way you want it to be by simple
> extending it.
>
> Thanks,
> Keith.
>
> On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) <jp...@avaya.com>wrote:
>
>> Hi,
>>
>> Does Axis2 include a class for transport listener which supports https?
>>
>> Is it possible to configure Axis2 to not include any port number when
>> generating the soap address?
>>
>> Thanks,
>> JP
>>
>> ------------------------------
>> *From:* Pugalia, Jai P (JP) [mailto:jpugalia@avaya.com]
>> *Sent:* Monday, September 22, 2008 4:10 PM
>> *To:* axis-user@ws.apache.org
>> *Subject:* RE: wsdl port address uses incorrect port number for https
>>
>> Hi,
>>
>> The proxyPort does not help us as we are not using Apache as a proxy
>> server.
>>
>> If I configure the axis2.xml as below:
>>
>> <transportReceiver name="http"
>> class="org.apache.axis2.transport.http.SimpleHTTPServer">
>> <parameter name="port">8080</parameter>
>> </transportReceiver>
>> <transportReceiver name="https" class="
>> org.apache.axis2.transport.http.SimpleHTTPServer">
>> <parameter name="port">8443</parameter>
>> </transportReceiver>
>>
>> then the soap address for http includes the port 8080 and the soap address
>> for https includes the port 8443 but the soap address itself is http and not
>> https.
>>
>> When should the class for transportReceiver be set to for https?
>>
>> If I do not specify the transportReceiver for https in axis2.xml, the the
>> default value of the port is taken as 80 instead of 443 which is the default
>> port for https.
>>
>> Thanks,
>> JP
>>
>> ------------------------------
>> *From:* keith chapman [mailto:keithgchapman@gmail.com]
>> *Sent:* Sunday, September 21, 2008 9:09 PM
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: wsdl port address uses incorrect port number for https
>>
>> It should be specified in the http transport listener of the axis2.xml.
>> You can have a look at
>> https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor an example usage. This is the axis2.xml used in the WSO2 Mashup Server
>> [1]
>>
>> Look for the following.
>>
>> <!--
>> Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80
>> in this case.
>> -->
>> <!--<parameter name="proxyPort">80</parameter>-->
>>
>>
>> Thanks,
>> Keith.
>>
>> [1] http://wso2.org/projects/mashup
>>
>> On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) <jp...@avaya.com>wrote:
>>
>>> Hi Keith,
>>>
>>> Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml,
>>> the http transport receiver has a port parameter is set to 8080 and the
>>> https transport receiver is commented out in axis2.xml. Am I heading in the
>>> right direction?
>>>
>>> Thanks,
>>> Jai
>>>
>>> ------------------------------
>>> *From:* keith chapman [mailto:keithgchapman@gmail.com]
>>> *Sent:* Sunday, September 21, 2008 10:02 AM
>>> *To:* axis-user@ws.apache.org
>>> *Subject:* Re: wsdl port address uses incorrect port number for https
>>>
>>> Hi,
>>>
>>> When its going through Apache you can use the following parameter in the
>>> transport listener to set the port address,
>>>
>>> <parameter name="proxyPort">80</parameter>
>>>
>>> For the https listener you can set it to 443.
>>>
>>> Thanks,
>>> Keith.
>>>
>>> On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <em...@hotmail.com>wrote:
>>>
>>>> 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 https
>>>> Date: Sun, 21 Sep 2008 09:51:13 -0600
>>>> From: jpugalia@avaya.com
>>>> To: 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:// <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:jpugalia@avaya.com<jp...@avaya.com>
>>>> ]
>>>> Sent: Fri 9/19/2008 8:52 AM
>>>> To: axis-user@ws.apache.org
>>>> Subject: RE: wsdl port address uses incorrect port number
>>>>
>>>> Hi Charitha,
>>>>
>>>> I am not including the wsdl with the aar file. Including the wsdl
>>>> causing 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 address
>>>> of the installed machine. The issue is port number is being set to a
>>>> wrong value. How does Axis2 determine what the port number should be set
>>>> to? Is there some way we can specify what the port number should be?
>>>>
>>>> Regards,
>>>> Jai
>>>>
>>>> -----Original Message-----
>>>> From: charitha kankanamge [mailto:charitha@wso2.com <ch...@wso2.com>
>>>> ]
>>>> Sent: Friday, September 19, 2008 8:24 AM
>>>> To: axis-user@ws.apache.org
>>>> Subject: Re: wsdl port address uses incorrect port number
>>>>
>>>> Hi,
>>>> You may set modifyUserWsdlPortAddress parameter to false in your
>>>> services.xml.
>>>>
>>>> <parameter name="*modifyUserWSDLPortAddress*">false</parameter>
>>>>
>>>> If you set this parameter to false and useoriginalWsdl set to true, the
>>>> port address specified in the original wsdl (wsdl included in META-INF
>>>> directory of your service archive) will be unchanged.
>>>>
>>>> regards
>>>> Charitha
>>>>
>>>> http://charithaka.blogspot.com
>>>> http://www.wso2.org
>>>>
>>>> Pugalia, 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: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------
>>>> Stay up to date on your PC, the Web, and your mobile phone with Windows
>>>> Live. See Now<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
>>>>
>>>
>>>
>>>
>>> --
>>> Keith Chapman
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> Oxygenating the Web Service Platform.
>>> http://wso2.org/
>>>
>>> blog: http://www.keith-chapman.org
>>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
RE: wsdl port address uses incorrect port number for https
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hi Keith,
For now, I had solved the problem by writing my own Listener by
implementing the TransportListener class. I like your suggestion of
extending the existing Listener so I am going to try it out.
I also tried by adding the proxyPort to the Connector configuration in
the server.xml of Tomcat, however looks like Axis2 does not use it and
instead takes a value of 80. I hope this gets fixed in future versions
of Axis2.
Thanks,
JP
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Wednesday, September 24, 2008 6:53 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https
You could easily extend the Listener shipped with Axis2 and override its
getEPRsForService method. This is the method that generates the endpoint
address, so you could handle it the way you want it to be by simple
extending it.
Thanks,
Keith.
On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP)
<jp...@avaya.com> wrote:
Hi,
Does Axis2 include a class for transport listener which supports
https?
Is it possible to configure Axis2 to not include any port number
when generating the soap address?
Thanks,
JP
________________________________
From: Pugalia, Jai P (JP) [mailto:jpugalia@avaya.com]
Sent: Monday, September 22, 2008 4:10 PM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number for
https
Hi,
The proxyPort does not help us as we are not using Apache as a
proxy server.
If I configure the axis2.xml as below:
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8080</parameter>
</transportReceiver>
<transportReceiver name="https"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8443</parameter>
</transportReceiver>
then the soap address for http includes the port 8080 and the
soap address for https includes the port 8443 but the soap address
itself is http and not https.
When should the class for transportReceiver be set to for https?
If I do not specify the transportReceiver for https in
axis2.xml, the the default value of the port is taken as 80 instead of
443 which is the default port for https.
Thanks,
JP
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for
https
It should be specified in the http transport listener of the
axis2.xml. You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]
Look for the following.
<!--
Uncomment the following to enable Apache2 mod_proxy. The
port on the Apache server is 80
in this case.
-->
<!--<parameter name="proxyPort">80</parameter>-->
Thanks,
Keith.
[1] http://wso2.org/projects/mashup
On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<jp...@avaya.com> wrote:
Hi Keith,
Where do I specify this parameter? I am guessing
axis2.xml. In axis2.xml, the http transport receiver has a port
parameter is set to 8080 and the https transport receiver is commented
out in axis2.xml. Am I heading in the right direction?
Thanks,
Jai
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port
number for https
Hi,
When its going through Apache you can use the following
parameter in the transport listener to set the port address,
<parameter name="proxyPort">80</parameter>
For the https listener you can set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<em...@hotmail.com> wrote:
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 https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: jpugalia@avaya.com
To: 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:// <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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect
port number
Hi Charitha,
I am not including the wsdl with the aar file.
Including the wsdl
causing 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 address
of the installed machine. The issue is port
number is being set to a
wrong value. How does Axis2 determine what the
port number should be set
to? Is there some way we can specify what the
port number should be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge
[mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect
port number
Hi,
You may set modifyUserWsdlPortAddress parameter
to false in your
services.xml.
<parameter
name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and
useoriginalWsdl set to true, the
port address specified in the original wsdl
(wsdl included in META-INF
directory of your service archive) will be
unchanged.
regards
Charitha
http://charithaka.blogspot.com
<http://charithaka.blogspot.com/>
http://www.wso2.org <http://www.wso2.org/>
Pugalia, 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:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
________________________________
Stay up to date on your PC, the Web, and your
mobile phone with Windows Live. See Now
<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: wsdl port address uses incorrect port number for https
Posted by keith chapman <ke...@gmail.com>.
You could easily extend the Listener shipped with Axis2 and override its
getEPRsForService method. This is the method that generates the endpoint
address, so you could handle it the way you want it to be by simple
extending it.
Thanks,
Keith.
On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) <jp...@avaya.com>wrote:
> Hi,
>
> Does Axis2 include a class for transport listener which supports https?
>
> Is it possible to configure Axis2 to not include any port number when
> generating the soap address?
>
> Thanks,
> JP
>
> ------------------------------
> *From:* Pugalia, Jai P (JP) [mailto:jpugalia@avaya.com]
> *Sent:* Monday, September 22, 2008 4:10 PM
> *To:* axis-user@ws.apache.org
> *Subject:* RE: wsdl port address uses incorrect port number for https
>
> Hi,
>
> The proxyPort does not help us as we are not using Apache as a proxy
> server.
>
> If I configure the axis2.xml as below:
>
> <transportReceiver name="http"
> class="org.apache.axis2.transport.http.SimpleHTTPServer">
> <parameter name="port">8080</parameter>
> </transportReceiver>
> <transportReceiver name="https" class="
> org.apache.axis2.transport.http.SimpleHTTPServer">
> <parameter name="port">8443</parameter>
> </transportReceiver>
>
> then the soap address for http includes the port 8080 and the soap address
> for https includes the port 8443 but the soap address itself is http and not
> https.
>
> When should the class for transportReceiver be set to for https?
>
> If I do not specify the transportReceiver for https in axis2.xml, the the
> default value of the port is taken as 80 instead of 443 which is the default
> port for https.
>
> Thanks,
> JP
>
> ------------------------------
> *From:* keith chapman [mailto:keithgchapman@gmail.com]
> *Sent:* Sunday, September 21, 2008 9:09 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: wsdl port address uses incorrect port number for https
>
> It should be specified in the http transport listener of the axis2.xml.
> You can have a look at
> https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor an example usage. This is the axis2.xml used in the WSO2 Mashup Server
> [1]
>
> Look for the following.
>
> <!--
> Uncomment the following to enable Apache2 mod_proxy. The port on the Apache server is 80
> in this case.
> -->
> <!--<parameter name="proxyPort">80</parameter>-->
>
> Thanks,
> Keith.
>
> [1] http://wso2.org/projects/mashup
>
> On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) <jp...@avaya.com>wrote:
>
>> Hi Keith,
>>
>> Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml,
>> the http transport receiver has a port parameter is set to 8080 and the
>> https transport receiver is commented out in axis2.xml. Am I heading in the
>> right direction?
>>
>> Thanks,
>> Jai
>>
>> ------------------------------
>> *From:* keith chapman [mailto:keithgchapman@gmail.com]
>> *Sent:* Sunday, September 21, 2008 10:02 AM
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: wsdl port address uses incorrect port number for https
>>
>> Hi,
>>
>> When its going through Apache you can use the following parameter in the
>> transport listener to set the port address,
>>
>> <parameter name="proxyPort">80</parameter>
>>
>> For the https listener you can set it to 443.
>>
>> Thanks,
>> Keith.
>>
>> On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <em...@hotmail.com>wrote:
>>
>>> 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 https
>>> Date: Sun, 21 Sep 2008 09:51:13 -0600
>>> From: jpugalia@avaya.com
>>> To: 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:// <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:jpugalia@avaya.com<jp...@avaya.com>
>>> ]
>>> Sent: Fri 9/19/2008 8:52 AM
>>> To: axis-user@ws.apache.org
>>> Subject: RE: wsdl port address uses incorrect port number
>>>
>>> Hi Charitha,
>>>
>>> I am not including the wsdl with the aar file. Including the wsdl
>>> causing 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 address
>>> of the installed machine. The issue is port number is being set to a
>>> wrong value. How does Axis2 determine what the port number should be set
>>> to? Is there some way we can specify what the port number should be?
>>>
>>> Regards,
>>> Jai
>>>
>>> -----Original Message-----
>>> From: charitha kankanamge [mailto:charitha@wso2.com <ch...@wso2.com>]
>>> Sent: Friday, September 19, 2008 8:24 AM
>>> To: axis-user@ws.apache.org
>>> Subject: Re: wsdl port address uses incorrect port number
>>>
>>> Hi,
>>> You may set modifyUserWsdlPortAddress parameter to false in your
>>> services.xml.
>>>
>>> <parameter name="*modifyUserWSDLPortAddress*">false</parameter>
>>>
>>> If you set this parameter to false and useoriginalWsdl set to true, the
>>> port address specified in the original wsdl (wsdl included in META-INF
>>> directory of your service archive) will be unchanged.
>>>
>>> regards
>>> Charitha
>>>
>>> http://charithaka.blogspot.com
>>> http://www.wso2.org
>>>
>>> Pugalia, 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: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>>
>>>
>>>
>>>
>>> ------------------------------
>>> Stay up to date on your PC, the Web, and your mobile phone with Windows
>>> Live. See Now<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
>>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
RE: wsdl port address uses incorrect port number for https
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hi,
Does Axis2 include a class for transport listener which supports https?
Is it possible to configure Axis2 to not include any port number when
generating the soap address?
Thanks,
JP
________________________________
From: Pugalia, Jai P (JP) [mailto:jpugalia@avaya.com]
Sent: Monday, September 22, 2008 4:10 PM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number for https
Hi,
The proxyPort does not help us as we are not using Apache as a proxy
server.
If I configure the axis2.xml as below:
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8080</parameter>
</transportReceiver>
<transportReceiver name="https"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8443</parameter>
</transportReceiver>
then the soap address for http includes the port 8080 and the soap
address for https includes the port 8443 but the soap address itself is
http and not https.
When should the class for transportReceiver be set to for https?
If I do not specify the transportReceiver for https in axis2.xml, the
the default value of the port is taken as 80 instead of 443 which is the
default port for https.
Thanks,
JP
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https
It should be specified in the http transport listener of the axis2.xml.
You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]
Look for the following.
<!--
Uncomment the following to enable Apache2 mod_proxy. The port on
the Apache server is 80
in this case.
-->
<!--<parameter name="proxyPort">80</parameter>-->
Thanks,
Keith.
[1] http://wso2.org/projects/mashup
On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<jp...@avaya.com> wrote:
Hi Keith,
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
Thanks,
Jai
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for
https
Hi,
When its going through Apache you can use the following
parameter in the transport listener to set the port address,
<parameter name="proxyPort">80</parameter>
For the https listener you can set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<em...@hotmail.com> wrote:
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 https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: jpugalia@avaya.com
To: 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:// <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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port
number
Hi Charitha,
I am not including the wsdl with the aar file. Including
the wsdl
causing 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 address
of the installed machine. The issue is port number is
being set to a
wrong value. How does Axis2 determine what the port
number should be set
to? Is there some way we can specify what the port
number should be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port
number
Hi,
You may set modifyUserWsdlPortAddress parameter to false
in your
services.xml.
<parameter
name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl
set to true, the
port address specified in the original wsdl (wsdl
included in META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com
<http://charithaka.blogspot.com/>
http://www.wso2.org <http://www.wso2.org/>
Pugalia, 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:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
________________________________
Stay up to date on your PC, the Web, and your mobile
phone with Windows Live. See Now
<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
RE: wsdl port address uses incorrect port number for https
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hi,
The proxyPort does not help us as we are not using Apache as a proxy
server.
If I configure the axis2.xml as below:
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8080</parameter>
</transportReceiver>
<transportReceiver name="https"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8443</parameter>
</transportReceiver>
then the soap address for http includes the port 8080 and the soap
address for https includes the port 8443 but the soap address itself is
http and not https.
When should the class for transportReceiver be set to for https?
If I do not specify the transportReceiver for https in axis2.xml, the
the default value of the port is taken as 80 instead of 443 which is the
default port for https.
Thanks,
JP
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https
It should be specified in the http transport listener of the axis2.xml.
You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]
Look for the following.
<!--
Uncomment the following to enable Apache2 mod_proxy. The port on
the Apache server is 80
in this case.
-->
<!--<parameter name="proxyPort">80</parameter>-->
Thanks,
Keith.
[1] http://wso2.org/projects/mashup
On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<jp...@avaya.com> wrote:
Hi Keith,
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
Thanks,
Jai
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for
https
Hi,
When its going through Apache you can use the following
parameter in the transport listener to set the port address,
<parameter name="proxyPort">80</parameter>
For the https listener you can set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<em...@hotmail.com> wrote:
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 https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: jpugalia@avaya.com
To: 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:// <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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port
number
Hi Charitha,
I am not including the wsdl with the aar file. Including
the wsdl
causing 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 address
of the installed machine. The issue is port number is
being set to a
wrong value. How does Axis2 determine what the port
number should be set
to? Is there some way we can specify what the port
number should be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port
number
Hi,
You may set modifyUserWsdlPortAddress parameter to false
in your
services.xml.
<parameter
name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl
set to true, the
port address specified in the original wsdl (wsdl
included in META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com
<http://charithaka.blogspot.com/>
http://www.wso2.org <http://www.wso2.org/>
Pugalia, 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:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail:
axis-user-help@ws.apache.org
________________________________
Stay up to date on your PC, the Web, and your mobile
phone with Windows Live. See Now
<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: wsdl port address uses incorrect port number for https
Posted by keith chapman <ke...@gmail.com>.
It should be specified in the http transport listener of the axis2.xml. You
can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor
an example usage. This is the axis2.xml used in the WSO2 Mashup Server
[1]
Look for the following.
<!--
Uncomment the following to enable Apache2 mod_proxy. The port
on the Apache server is 80
in this case.
-->
<!--<parameter name="proxyPort">80</parameter>-->
Thanks,
Keith.
[1] http://wso2.org/projects/mashup
On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) <jp...@avaya.com>wrote:
> Hi Keith,
>
> Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml,
> the http transport receiver has a port parameter is set to 8080 and the
> https transport receiver is commented out in axis2.xml. Am I heading in the
> right direction?
>
> Thanks,
> Jai
>
> ------------------------------
> *From:* keith chapman [mailto:keithgchapman@gmail.com]
> *Sent:* Sunday, September 21, 2008 10:02 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: wsdl port address uses incorrect port number for https
>
> Hi,
>
> When its going through Apache you can use the following parameter in the
> transport listener to set the port address,
>
> <parameter name="proxyPort">80</parameter>
>
> For the https listener you can set it to 443.
>
> Thanks,
> Keith.
>
> On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <em...@hotmail.com>wrote:
>
>> 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 https
>> Date: Sun, 21 Sep 2008 09:51:13 -0600
>> From: jpugalia@avaya.com
>> To: 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:// <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:jpugalia@avaya.com <jp...@avaya.com>
>> ]
>> Sent: Fri 9/19/2008 8:52 AM
>> To: axis-user@ws.apache.org
>> Subject: RE: wsdl port address uses incorrect port number
>>
>> Hi Charitha,
>>
>> I am not including the wsdl with the aar file. Including the wsdl
>> causing 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 address
>> of the installed machine. The issue is port number is being set to a
>> wrong value. How does Axis2 determine what the port number should be set
>> to? Is there some way we can specify what the port number should be?
>>
>> Regards,
>> Jai
>>
>> -----Original Message-----
>> From: charitha kankanamge [mailto:charitha@wso2.com <ch...@wso2.com>]
>> Sent: Friday, September 19, 2008 8:24 AM
>> To: axis-user@ws.apache.org
>> Subject: Re: wsdl port address uses incorrect port number
>>
>> Hi,
>> You may set modifyUserWsdlPortAddress parameter to false in your
>> services.xml.
>>
>> <parameter name="*modifyUserWSDLPortAddress*">false</parameter>
>>
>> If you set this parameter to false and useoriginalWsdl set to true, the
>> port address specified in the original wsdl (wsdl included in META-INF
>> directory of your service archive) will be unchanged.
>>
>> regards
>> Charitha
>>
>> http://charithaka.blogspot.com
>> http://www.wso2.org
>>
>> Pugalia, 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: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>>
>> ------------------------------
>> Stay up to date on your PC, the Web, and your mobile phone with Windows
>> Live. See Now<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
>>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
RE: wsdl port address uses incorrect port number for https
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hi Keith,
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
Thanks,
Jai
________________________________
From: keith chapman [mailto:keithgchapman@gmail.com]
Sent: Sunday, September 21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https
Hi,
When its going through Apache you can use the following parameter in the
transport listener to set the port address,
<parameter name="proxyPort">80</parameter>
For the https listener you can set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <em...@hotmail.com>
wrote:
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
https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: jpugalia@avaya.com
To: 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:// <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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number
Hi Charitha,
I am not including the wsdl with the aar file. Including the
wsdl
causing 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
address
of the installed machine. The issue is port number is being set
to a
wrong value. How does Axis2 determine what the port number
should be set
to? Is there some way we can specify what the port number should
be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number
Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.
<parameter name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl set to
true, the
port address specified in the original wsdl (wsdl included in
META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com <http://charithaka.blogspot.com/>
http://www.wso2.org <http://www.wso2.org/>
Pugalia, 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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
________________________________
Stay up to date on your PC, the Web, and your mobile phone with
Windows Live. See Now
<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: wsdl port address uses incorrect port number for https
Posted by keith chapman <ke...@gmail.com>.
Hi,
When its going through Apache you can use the following parameter in the
transport listener to set the port address,
<parameter name="proxyPort">80</parameter>
For the https listener you can set it to 443.
Thanks,
Keith.
On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <em...@hotmail.com>wrote:
> 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 https
> Date: Sun, 21 Sep 2008 09:51:13 -0600
> From: jpugalia@avaya.com
> To: 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:// <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:jpugalia@avaya.com <jp...@avaya.com>]
> Sent: Fri 9/19/2008 8:52 AM
> To: axis-user@ws.apache.org
> Subject: RE: wsdl port address uses incorrect port number
>
> Hi Charitha,
>
> I am not including the wsdl with the aar file. Including the wsdl
> causing 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 address
> of the installed machine. The issue is port number is being set to a
> wrong value. How does Axis2 determine what the port number should be set
> to? Is there some way we can specify what the port number should be?
>
> Regards,
> Jai
>
> -----Original Message-----
> From: charitha kankanamge [mailto:charitha@wso2.com <ch...@wso2.com>]
> Sent: Friday, September 19, 2008 8:24 AM
> To: axis-user@ws.apache.org
> Subject: Re: wsdl port address uses incorrect port number
>
> Hi,
> You may set modifyUserWsdlPortAddress parameter to false in your
> services.xml.
>
> <parameter name="*modifyUserWSDLPortAddress*">false</parameter>
>
> If you set this parameter to false and useoriginalWsdl set to true, the
> port address specified in the original wsdl (wsdl included in META-INF
> directory of your service archive) will be unchanged.
>
> regards
> Charitha
>
> http://charithaka.blogspot.com
> http://www.wso2.org
>
> Pugalia, 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
> ------------------------------
> Stay up to date on your PC, the Web, and your mobile phone with Windows
> Live. See Now<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
RE: wsdl port address uses incorrect port number for https
Posted by Enaganti M Naidu <em...@hotmail.com>.
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: jpugalia@avaya.comTo: 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:jpugalia@avaya.com]Sent: Fri 9/19/2008 8:52 AMTo: axis-user@ws.apache.orgSubject: 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:charitha@wso2.com]Sent: Friday, September 19, 2008 8:24 AMTo: axis-user@ws.apache.orgSubject: 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: axis-user-unsubscribe@ws.apache.orgFor additional commands, e-mail: axis-user-help@ws.apache.org---------------------------------------------------------------------To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.orgFor additional commands, e-mail: axis-user-help@ws.apache.org
_________________________________________________________________
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/
RE: wsdl port address uses incorrect port number for https
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
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:jpugalia@avaya.com]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number
Hi Charitha,
I am not including the wsdl with the aar file. Including the wsdl
causing 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 address
of the installed machine. The issue is port number is being set to a
wrong value. How does Axis2 determine what the port number should be set
to? Is there some way we can specify what the port number should be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number
Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.
<parameter name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl set to true, the
port address specified in the original wsdl (wsdl included in META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com
http://www.wso2.org
Pugalia, 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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: wsdl port address uses incorrect port number
Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hi Charitha,
I am not including the wsdl with the aar file. Including the wsdl
causing 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 address
of the installed machine. The issue is port number is being set to a
wrong value. How does Axis2 determine what the port number should be set
to? Is there some way we can specify what the port number should be?
Regards,
Jai
-----Original Message-----
From: charitha kankanamge [mailto:charitha@wso2.com]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number
Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.
<parameter name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl set to true, the
port address specified in the original wsdl (wsdl included in META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com
http://www.wso2.org
Pugalia, 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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: wsdl port address uses incorrect port number
Posted by charitha kankanamge <ch...@wso2.com>.
Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.
<parameter name="*modifyUserWSDLPortAddress*">false</parameter>
If you set this parameter to false and useoriginalWsdl set to true, the
port address specified in the original wsdl (wsdl included in META-INF
directory of your service archive) will be unchanged.
regards
Charitha
http://charithaka.blogspot.com
http://www.wso2.org
Pugalia, 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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org