Thanks Andreas for pointing me to the jira.
I was wondering whether there is a programmatic way of setting the
address location in axis2. The use case is that a client would like to
have a fqdn in the address rather than an IP.
Can you point me to the class(es) that are currently setting the address
location?
-Alex
On 27.05.2010 17:39, Andreas Veithen wrote:
There are known issues with generating endpoint references for HTTPS
in Axis2. This has been fixed by AXIS2-4465.
Andreas
On Thu, May 27, 2010 at 16:58, Alexander Rosemann
<[email protected]> wrote:
Hi,
I configured a service to use a hand written WSDL contract. Axis shows the
contract as expected but displays the wrong port for the address location.
I'm running Axis2 1.4.1 included in a web-app in Tomcat 6.0.20 using HTTPS,
port 8443.
That's what I get:
<soap:address
location="http://192.168.1.102:8080/myapp/services/superservice/"/>
and that's what I would expect:
<soap:address
location="http://192.168.1.102:8443/myapp/services/superservice/"/>
Any clues why this is happening and how I can fix this?
Best,
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
