Ok, dims thanks. I'll do that.

Anyway I'm probably going for a 'Contract-First' approach. But it's
possible that we have clients using our WS from the internet (public IP
address) and from our LAN (private IP address). and that case is a
problem because with need to put a handcoded location in our WSDL (one
IP or the other).

You clarified it a lot to me.

Thanks for your help again.

Luis

Davanum Srinivas escribió:
> Luis,
>
> You best bet for Axis2 1.2 release would be to save the autogenerated
> file and use the modifyUserWSDLPortAddress / useOriginalwsdl in
> services.xml. Please raise an issue in JIRA for an alternate mechanism
> say supply the host name in web.xml servlet init parameters for system
> wide use. Sorry about that.
>
> -- dims
>
> On 5/28/07, Luis Mariano Luporini <[EMAIL PROTECTED]> wrote:
>> Great dims, I tried it and worked. Although, it worked for user provided
>> WSDL and not for Autogenerated (for example in case of POJO based
>> service).
>>
>> Is there any alternative or some setting axis2 wide?
>>
>> Thanks for your help.
>>
>>
>> Davanum Srinivas escribió:
>> > See http://wso2.org/blog/dims/1572
>> >
>> > -- dims
>> >
>> > On 5/28/07, Luis Mariano Luporini <[EMAIL PROTECTED]> wrote:
>> >> Hi:
>> >>
>> >>     I'm using Tomcat 6 on port 8080 with Axis 1.2.
>> >>
>> >>     My server is a LAN with one NIC and just one private IP address.
>> >> Let's say: 192.168.10.10/24.
>> >>
>> >>     I using a firewall conected to the Internat which has a public IP
>> >> address: Let's say: 200.0.0.1/24.
>> >>
>> >>     When a client connects to my services "Autogenerated WSDL"
>> they get
>> >> all http locations (soap:address) refering to my internal IP address,
>> >> that is 'http://192.168.10.10:8080/services/xxxx?wsdl'
>> >>
>> >>     I need a way to instruct Axis to put my public IP address when
>> the
>> >> 'Auto Generated WSDL' is served.
>> >>
>> >>     I read previously the same situation in this thread:
>> >> http://marc.info/?t=117951431900006&r=1&w=2 but it doesn't come to a
>> >> close.
>> >>
>> >>     I tried enabling and changing the hostname parameter in axis2.xml
>> >> inside tag <transportReceiver name="http"
>> >> class="org.apache.axis2.transport.http.SimpleHTTPServer">, but
>> this did
>> >> not change any behaviour in my 'Autogenerated WSDL'. I think this is
>> >> because I'm not using SimpleAxisServer, just Axis2 on Tomcat as told
>> >> above.
>> >>
>> >>     I having a hard time trying to get more info on the net about it.
>> >>
>> >>     If anyone can help, this will be much appreciated.
>> >>
>> >>     Thanks in advance,
>> >>
>> >> Regards,
>> >>
>> >> Luis
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> -------- Mensaje original --------
>> >> Asunto:         Re: How does axis decide the endpoint URL?
>> >> Fecha:  Mon, 28 May 2007 04:36:30 -0300
>> >> De:     Luis Mariano Luporini <[EMAIL PROTECTED]>
>> >> Para:   [email protected]
>> >> Referencias:    <[EMAIL PROTECTED]>
>> >>
>> >>
>> >>
>> >> Jeremy:
>> >>
>> >> I'm having the same problem right now. I'm working on Tomcat and not
>> >> using SimpleAxisServer.
>> >>
>> >> Changing the hostname parameter value did not make any effect.
>> >>
>> >> Did you manage to solve it?
>> >>
>> >> Thanks in advance,
>> >>
>> >> Luis
>> >>
>> >> -----
>> >>
>> >> 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"/
>> >> <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"/
>> >> <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"/
>> >> <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]
>> >>
>> >>
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> 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