But is there an option to control the *host* of the services? I am getting an inaccessible address for the hostname of the service endpoint (i.e. http://10.x.x.x/axis2/etc) but I want to have a proper domain name in there (i.e. http://my.domain.com/axis2/etc).

Is this possible?

Thanks,
Jeremy

Martin Gainty wrote:
as Dims pomited out you can see the web.xml servlet parameters (located in WEB-INF)

in the case of services AxisServlet will be invoked
  <servlet-mapping>
       <servlet-name>AxisServlet</servlet-name>
       <url-pattern>/services/*</url-pattern>
   </servlet-mapping>
   <servlet>
       <servlet-name>AxisServlet</servlet-name>
       <display-name>Apache-Axis Servlet</display-name>
       <servlet-class>
           org.apache.axis2.transport.http.AxisServlet</servlet-class>
       </servlet-class>
   </servlet>

//or with rest AxisRESTServlet will be invoked..
   <servlet-mapping>
       <servlet-name>AxisRESTServlet</servlet-name>
       <url-pattern>/rest/*</url-pattern>
   </servlet-mapping>
   <servlet>
       <servlet-name>AxisRESTServlet</servlet-name>
       <display-name>Apache-Axis Servlet (REST)</display-name>
       <servlet-class>
org.apache.axis2.transport.http.AxisRESTServlet</servlet-class>
   </servlet>

HTH/
Martin
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

----- Original Message ----- From: "Davanum Srinivas" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, May 18, 2007 3:11 PM
Subject: Re: How does axis decide the endpoint URL?


Please look into your axis2.xml under WEB-INF/conf there is a setting
there for hard-coding the url.

thanks,
dims

On 5/18/07, Jeremy Smith <[EMAIL PROTECTED]> wrote:
My server has a bit of a complicated networking setup.  It is behind a
firewall with an external address, and it only knows about its internal
addresses.  The problem is that in the wsdl that axis2 generates, it
directs clients to the internal URL and they can't connect.

How does axis2 decide what the URL will be?  Is there any way I can
override this?

Example:


Axis generates this:

<wsdl:service name="MyService">
    <wsdl:port name="MyServiceSOAP11port_http"
binding="axis2:MyServiceSOAP11Binding">
       <soap:address
location="http://10.x.x.x:80/axis2/services/MyService"/>
    </wsdl:port>
    <wsdl:port name="MyServiceSOAP12port_http"
binding="axis2:MyServiceSOAP12Binding">
        <soap12:address
location="http://10.x.x.x:80/axis2/services/MyService"/>
    </wsdl:port>
    <wsdl:port name="MyServiceHttpport"
binding="axis2:MyServiceHttpBinding">
        <http:address
location="http://10.x.x.x:80/axis2/services/MyService"/>
    </wsdl:port>
</wsdl:service>

where 10.x.x.x is an inaccessible internal IP address.

Thanks,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
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]

Reply via email to