Re: [AXIS2] soap:address location under a Frontend
Someone has some suggestions, even to put a customized WSDL (with replaced front-ends) in the AAR? Thanks. manub wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService − wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port − wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port − wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23651580.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [AXIS2] soap:address location under a Frontend
p.s. I'm using Axis2 1.2 manub wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService − wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port − wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port − wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631967.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [AXIS2] soap:address location under a Frontend
Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23635646.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
I tried, before parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er, to insert a parameter like parameter name=hostname locked=truehttps://myFrontend:myPort//parameter but it still doesn't work. Can you suggest me something? Searching into google I know you addressed same problem as mine, some time ago. Thanks. Raghu Upadhyayula wrote: Hi Manub, You can change the hostname in the soap:address location in your wsdl by specifying the hostname parameter in axis2.xml. Let me know if this is sufficient for you, if not there is also a way to change the hostname parameter programmatically. Thanks Raghu -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wednesday, May 20, 2009 8:40 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23635646.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23635988.html Sent from the Axis - User mailing list archive at Nabble.com.
