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 > > name="httpFrontendHostUrl">https://myFrontend:myPort/myServices > > but in the autogenerated WSDL, still got > > > − > binding="axis2:myServiceSOAP11Binding"> > location="http://myInternalIp:myPort/myServices/services/myService"/> > > − > binding="axis2:myServiceSOAP12Binding"> > location="http://myInternalIp:myPort/myServices/services/myService"/> > > − > > location="http://myInternalIp:myPort/myServices/services/myService"/> > > > > > 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
I agree with Andreas in principle, but I don't know if anyone out there has a specific use case for the 3rd option? Neil Youngman -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Wed 20-May-09 15:11 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend While working on AXIS2-3843, I had a closer look at the code and this is what should work and what doesn't work: - httpFrontendHostUrl is not supported, neither by the servlet based HTTP transport, nor by SimpleHTTPServer. It is only used by the JSP pages of the admin console. - hostname, when specified at the global level in axis2.xml should allow to specify the hostname part. This should work with both transports, but it is not sufficient in this case (because http needs to be substituted by https). - hostname, when specified as a parameter of the SimpleHTTPServer transport receiver, allows to specify the URL. This is not supported by the servlet based transport. I think that we should modify both transports to support httpFrontendHostUrl. The hostname parameter as described in the 2nd point should remain because it's scope is not limited to the HTTP transports. The question is what to do with the hostname parameter in the 3rd option. I think that we should eliminate this one (in favor of httpFrontendHostUrl) because it is very misleading, both because of its name (it's not a hostname, but a URL) and because of the existence of another hostname parameter at the global level. Any thoughts? Andreas On Wed, May 20, 2009 at 15:56, manub wrote: > > I tried, before name="httpFrontendHostUrl">https://myFrontend:myPort/myServices er>, to insert a parameter like > > locked="true">https://myFrontend:myPort/ > > 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=6965056&postcount=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: >>>>>
RE: [AXIS2] soap:address location under a Frontend
In my case I just changed it like this myFrontEnd and it worked. Instead of myFrontEnd if I give the value as http://myFrontEnd then that whole string is appearing as it is in the soap:address location and it is showing the soap:address location as http://http://myFrontEnd which is wrong, so I've changed it to just have the hostname. -Raghu -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Wednesday, May 20, 2009 9:12 AM To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend While working on AXIS2-3843, I had a closer look at the code and this is what should work and what doesn't work: - httpFrontendHostUrl is not supported, neither by the servlet based HTTP transport, nor by SimpleHTTPServer. It is only used by the JSP pages of the admin console. - hostname, when specified at the global level in axis2.xml should allow to specify the hostname part. This should work with both transports, but it is not sufficient in this case (because http needs to be substituted by https). - hostname, when specified as a parameter of the SimpleHTTPServer transport receiver, allows to specify the URL. This is not supported by the servlet based transport. I think that we should modify both transports to support httpFrontendHostUrl. The hostname parameter as described in the 2nd point should remain because it's scope is not limited to the HTTP transports. The question is what to do with the hostname parameter in the 3rd option. I think that we should eliminate this one (in favor of httpFrontendHostUrl) because it is very misleading, both because of its name (it's not a hostname, but a URL) and because of the existence of another hostname parameter at the global level. Any thoughts? Andreas On Wed, May 20, 2009 at 15:56, manub wrote: > > I tried, before name="httpFrontendHostUrl">https://myFrontend:myPort/myServices er>, to insert a parameter like > > locked="true">https://myFrontend:myPort/ > > 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=6965056&postcount=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). >>>>
Re: [AXIS2] soap:address location under a Frontend
While working on AXIS2-3843, I had a closer look at the code and this is what should work and what doesn't work: - httpFrontendHostUrl is not supported, neither by the servlet based HTTP transport, nor by SimpleHTTPServer. It is only used by the JSP pages of the admin console. - hostname, when specified at the global level in axis2.xml should allow to specify the hostname part. This should work with both transports, but it is not sufficient in this case (because http needs to be substituted by https). - hostname, when specified as a parameter of the SimpleHTTPServer transport receiver, allows to specify the URL. This is not supported by the servlet based transport. I think that we should modify both transports to support httpFrontendHostUrl. The hostname parameter as described in the 2nd point should remain because it's scope is not limited to the HTTP transports. The question is what to do with the hostname parameter in the 3rd option. I think that we should eliminate this one (in favor of httpFrontendHostUrl) because it is very misleading, both because of its name (it's not a hostname, but a URL) and because of the existence of another hostname parameter at the global level. Any thoughts? Andreas On Wed, May 20, 2009 at 15:56, manub wrote: > > I tried, before name="httpFrontendHostUrl">https://myFrontend:myPort/myServices er>, to insert a parameter like > > locked="true">https://myFrontend:myPort/ > > 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=6965056&postcount=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 wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I need to expose some webservices via
RE: [AXIS2] soap:address location under a Frontend
I tried, before https://myFrontend:myPort/myServices, to insert a parameter like https://myFrontend:myPort/ 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=6965056&postcount=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 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 >>>>> >>>>>>>>> > name="httpFrontendHostUrl">https://myFrontend:myPort/myServices er> >>>>> >>>>> but in the autogenerated WSDL, still got >>>>> >>>>> >>>>> - >>>>> >>>> binding="axis2:myServiceSOAP11Binding"> >>>>> >>>> > location="http://myInternalIp:myPort/myServices/services/myService"/> >>>>> >>>>> - >>>>> >>>> binding="axis2:myServiceSOAP12Binding"> >>>>> >>>> > location="http://myInternalIp:myPort/myServices/services/myService"/> >>>>> >>>>> - >>>>> >>>> binding="axis2:myServiceHttpBinding"> >>>>> >>>> > location="http://myInternalIp:myPort/myServices/services/myService"/> >>>>> >>>>> >>>>> >>>>> >>>>> 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.
RE: [AXIS2] soap:address location under a Frontend
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=6965056&postcount=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 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 >>>> >>>>>>> name="httpFrontendHostUrl">https://myFrontend:myPort/myServices >>>> >>>> but in the autogenerated WSDL, still got >>>> >>>> >>>> - >>>> >>> binding="axis2:myServiceSOAP11Binding"> >>>> >>> location="http://myInternalIp:myPort/myServices/services/myService"/> >>>> >>>> - >>>> >>> binding="axis2:myServiceSOAP12Binding"> >>>> >>> location="http://myInternalIp:myPort/myServices/services/myService"/> >>>> >>>> - >>>> >>> binding="axis2:myServiceHttpBinding"> >>>> >>> location="http://myInternalIp:myPort/myServices/services/myService"/> >>>> >>>> >>>> >>>> >>>> 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.
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=6965056&postcount=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 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 >>>> >>>>>>> name="httpFrontendHostUrl">https://myFrontend:myPort/myServices >>>> >>>> but in the autogenerated WSDL, still got >>>> >>>> >>>> - >>>> >>> binding="axis2:myServiceSOAP11Binding"> >>>> >>> location="http://myInternalIp:myPort/myServices/services/myService"/> >>>> >>>> - >>>> >>> binding="axis2:myServiceSOAP12Binding"> >>>> >>> location="http://myInternalIp:myPort/myServices/services/myService"/> >>>> >>>> - >>>> >>> binding="axis2:myServiceHttpBinding"> >>>> >>> location="http://myInternalIp:myPort/myServices/services/myService"/> >>>> >>>> >>>> >>>> >>>> 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
There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056&postcount=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 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 >>> >>>>> name="httpFrontendHostUrl">https://myFrontend:myPort/myServices >>> >>> but in the autogenerated WSDL, still got >>> >>> >>> - >>> >> binding="axis2:myServiceSOAP11Binding"> >>> >> location="http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> - >>> >> binding="axis2:myServiceSOAP12Binding"> >>> >> location="http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> - >>> >> binding="axis2:myServiceHttpBinding"> >>> >> location="http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> >>> >>> >>> 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
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 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 >>> >>>>> name="httpFrontendHostUrl">https://myFrontend:myPort/myServices >>> >>> but in the autogenerated WSDL, still got >>> >>> >>> - >>> >> binding="axis2:myServiceSOAP11Binding"> >>> >> location="http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> - >>> >> binding="axis2:myServiceSOAP12Binding"> >>> >> location="http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> - >>> >> binding="axis2:myServiceHttpBinding"> >>> >> location="http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> >>> >>> >>> 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
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 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 >> >>> name="httpFrontendHostUrl">https://myFrontend:myPort/myServices >> >> but in the autogenerated WSDL, still got >> >> >> - >> > binding="axis2:myServiceSOAP11Binding"> >> > location="http://myInternalIp:myPort/myServices/services/myService"/> >> >> - >> > binding="axis2:myServiceSOAP12Binding"> >> > location="http://myInternalIp:myPort/myServices/services/myService"/> >> >> - >> >> > location="http://myInternalIp:myPort/myServices/services/myService"/> >> >> >> >> >> 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
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 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 >> >>> name="httpFrontendHostUrl">https://myFrontend:myPort/myServices >> >> but in the autogenerated WSDL, still got >> >> >> - >> > binding="axis2:myServiceSOAP11Binding"> >> > location="http://myInternalIp:myPort/myServices/services/myService"/> >> >> - >> > binding="axis2:myServiceSOAP12Binding"> >> > location="http://myInternalIp:myPort/myServices/services/myService"/> >> >> - >> >> > location="http://myInternalIp:myPort/myServices/services/myService"/> >> >> >> >> >> 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
We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, 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 > > name="httpFrontendHostUrl">https://myFrontend:myPort/myServices > > but in the autogenerated WSDL, still got > > > - > binding="axis2:myServiceSOAP11Binding"> > location="http://myInternalIp:myPort/myServices/services/myService"/> > > - > binding="axis2:myServiceSOAP12Binding"> > location="http://myInternalIp:myPort/myServices/services/myService"/> > > - > > location="http://myInternalIp:myPort/myServices/services/myService"/> > > > > > 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. > >
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 > > name="httpFrontendHostUrl">https://myFrontend:myPort/myServices > > but in the autogenerated WSDL, still got > > > − > binding="axis2:myServiceSOAP11Binding"> > location="http://myInternalIp:myPort/myServices/services/myService"/> > > − > binding="axis2:myServiceSOAP12Binding"> > location="http://myInternalIp:myPort/myServices/services/myService"/> > > − > > location="http://myInternalIp:myPort/myServices/services/myService"/> > > > > > 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.