Deepal,
Ok, fair enough, I can do that. But to clarify my original point (which
was not clear enough):
1) can I remove what I consider to be unnecessary ports in the WSDL and
also prevent AXIS2 from providing services on those ports?
2) the WSDL that appears references IPs that are not active --
192.168.2.10? This is also confusing my client. Axis2 1.1.1 referenced
localhost usually when I used that...
Thanks.
VJ
Deepal Jayasinghe wrote:
You can pick either one you want :)
we generate multiple ports for different transports , so if you want
http then select port which has http portAddress .
Thanks
Deepal
Vickram Jain wrote:
I've just upgraded to Axis2 1.2 for an existing set of service
developed and deployed under 1.1.1. I include a WSDL file that I
created in my aar -- but it now generates additional ports as below:
- <#> <wsdl:service name="*MyService*">
- <#> <wsdl:port name="*MyServiceSOAP11port_http*"
binding="*fc:MyServiceSOAP11Binding*">
<soap:address
location="*http://192.168.2.10:8080/axis2/services/MyService*"; />
</wsdl:port>
- <#> <wsdl:port name="*MyServiceSOAP11port_tcp1*"
binding="*fc:MyServiceSOAP11Binding*">
<soap:address
location="*tcp://192.168.2.10:6061/axis2/services/MyService*" />
</wsdl:port>
- <#> <wsdl:port name="*MyServiceSOAP12port_http*"
binding="*fc:MyServiceSOAP12Binding*">
<soap12:address
location="*http://192.168.2.10:8080/axis2/services/MyService*"; />
</wsdl:port>
- <#> <wsdl:port name="*MyServiceSOAP12port_tcp1*"
binding="*fc:MyServiceSOAP12Binding*">
<soap12:address
location="*tcp://192.168.2.10:6061/axis2/services/MyService*" />
</wsdl:port>
- <#> <wsdl:port name="*MyServiceHttpport*"
binding="*fc:MyServiceHttpBinding*">
<http:address
location="*http://192.168.2.10:8080/axis2/services/MyService*"; />
</wsdl:port>
The "_tcp1" ports were not in the WSDL generated in 1.1.1 -- my
(non-AXIS) client gets confused now because it cannot determine which
is the default SOAP11 or SOAP12 binding it should use (that's what it
says at least). Is this customizable somehow?
Thanks,
Vickram
