Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 67406 invoked from network); 20 May 2009 12:03:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 May 2009 12:03:54 -0000 Received: (qmail 5057 invoked by uid 500); 20 May 2009 12:04:05 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 5001 invoked by uid 500); 20 May 2009 12:04:05 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 4992 invoked by uid 99); 20 May 2009 12:04:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2009 12:04:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [82.71.224.237] (HELO mail.wirefast.com) (82.71.224.237) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 20 May 2009 12:03:55 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9D942.FEE5BFE6" Subject: RE: [AXIS2] soap:address location under a Frontend Date: Wed, 20 May 2009 13:02:27 +0100 Message-ID: <41ACF455477C0047BB8537E0A092794E01582F10@mail.wire2.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [AXIS2] soap:address location under a Frontend Thread-Index: AcnZOov0LMyFBeHmRlWGE5gZTaShagACEwtU References: <23631957.post@talk.nabble.com> <23632085.post@talk.nabble.com> <41ACF455477C0047BB8537E0A092794E01582F0D@mail.wire2.com> <23633294.post@talk.nabble.com> From: "Neil Youngman" To: X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C9D942.FEE5BFE6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable There's a suggestion at = http://archives.devshed.com/forums/showpost.php?p=3D6965056&postcount=3D6= but I couldn't get it to work. Neil Youngman -----Original Message----- From: manub [mailto:e.blanco@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend =20 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: >=20 > I went through this quite recently. Nobody was able to give me a = solution, > so I posted a suggested patch at=20 > https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable > patching the code yourself? >=20 > Neil >=20 >=20 > -----Original Message----- > From: manub [mailto:e.blanco@reply.it] > Sent: Wed 20-May-09 10:35 > To: axis-user@ws.apache.org > Subject: Re: [AXIS2] soap:address location under a Frontend > =20 >=20 > 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). >=20 > No other ways to get it to work, even manually tweaking something? >=20 > Thank you. >=20 >=20 > Andreas Veithen-2 wrote: >>=20 >> We are working on this. See AXIS2-3843. >>=20 >> Andreas >>=20 >> 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=3D"httpFrontendHostUrl">https://myFrontend:myPort/myServices >>> >>> but in the autogenerated WSDL, still got >>> >>> >>> - >>> >> binding=3D"axis2:myServiceSOAP11Binding"> >>> >> = location=3D"http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> - >>> >> binding=3D"axis2:myServiceSOAP12Binding"> >>> >> = location=3D"http://myInternalIp:myPort/myServices/services/myService"/> >>> >>> - >>> >> binding=3D"axis2:myServiceHttpBinding"> >>> >> = location=3D"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-tp= 23631957p23631957.html >>> Sent from the Axis - User mailing list archive at Nabble.com. >>> >>> >>=20 >>=20 >=20 > --=20 > View this message in context: > = http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp= 23631957p23632085.html > Sent from the Axis - User mailing list archive at Nabble.com. >=20 >=20 >=20 > =20 >=20 --=20 View this message in context: = http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp= 23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com. ------_=_NextPart_001_01C9D942.FEE5BFE6 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [AXIS2] soap:address location under a Frontend

There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=3D6965056&pos= tcount=3D6 but I couldn't get it to work.

Neil Youngman


-----Original Message-----
From: manub [mailto:e.blanco@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.blanco@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.blanco@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=3D"httpFrontendHostUrl">https://myFrontend:myPort/m= yServices</parameter>
>>>
>>> but in the autogenerated WSDL, still got
>>>
>>> <wsdl:service name=3D"myService">
>>> -
>>> <wsdl:port = name=3D"myServiceSOAP11port_http"
>>> binding=3D"axis2:myServiceSOAP11Binding">
>>> <soap:address
>>> location=3D"http://= myInternalIp:myPort/myServices/services/myService"/>
>>> </wsdl:port>
>>> -
>>> <wsdl:port = name=3D"myServiceSOAP12port_http"
>>> binding=3D"axis2:myServiceSOAP12Binding">
>>> <soap12:address
>>> location=3D"http://= myInternalIp:myPort/myServices/services/myService"/>
>>> </wsdl:port>
>>> -
>>> <wsdl:port name=3D"myServiceHttpport"
>>> binding=3D"axis2:myServiceHttpBinding">
>>> <http:address
>>> location=3D"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%3Aaddr= ess-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%3Aaddr= ess-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%3Aaddr= ess-location-under-a-Frontend-tp23631957p23633294.html
Sent from the Axis - User mailing list archive at Nabble.com.

------_=_NextPart_001_01C9D942.FEE5BFE6--