Hi,
thx for the response.
Looking on the internet it seems that these parameters also existed before
1.4.1. ?
But we never used them in 1.4.1 and always got the orginal wsdl back (no
modif of WSDLPortAddress) !?
Strange ?
Amila Suriarachchi wrote:
>
> set following properties in services.xml
>
> true
> false
>
> thanks,
> Amila.
>
> On Mon, Nov 2, 2009 at 10:29 PM, SGE0 wrote:
>
>>
>> Hi,
>>
>> we encounter following problem:
>>
>> In version 1.4.1 we needed to generate the wsdl file and put it in the
>> services/ folder so a customer asking the wsdl content got back the wsdl
>> file content (and not a wsdl generated based on the services.xml file).
>> The
>> reason is that if the Axis2 context is behind a proxy (there is a
>> difference between the internal and external address the customer calls)
>> it
>> should be possible to put the external address in the wsdl.
>>
>> In version 1.5.1 we see a behavioral change. We have the impression that
>> the
>> wsdl is again generated from the services.xml file (as the soapaddress in
>> the wsdl the customer gets back is not the address defined in the wsdl
>> file
>> we generated).
>>
>>
>> Is this correct ? If so, how can we have the same behavior as in v1.4.1 ?
>>
>> This is blocking for us to upgrade. We must be able to pass the customer
>> the
>> external 'proxy' address and not the internal ip-address (which is behind
>> the proxy and has no value for the customer).
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Problem-upgrading-from-Axis2-Java-1.4.1-to-1.5.1-tp26157742p26157742.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
>
--
View this message in context:
http://old.nabble.com/Problem-upgrading-from-Axis2-Java-1.4.1-to-1.5.1-tp26157742p26195184.html
Sent from the Axis - User mailing list archive at Nabble.com.