You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Chinmoy Chakraborty <cc...@gmail.com> on 2008/10/21 16:14:15 UTC

Different address location in WSDL generated by Axis2

 Hi All,

Following is my service portion of the WSDL of service ABS generated by
Axis2 1.4.
....................
<wsdl:service name="ABS">
<wsdl:port name="ABSHttpSoap11Endpoint" binding="ns:ABSSoap11Binding">
<soap:address location="
http://192.168.1.54:8080/services/ABS.ABSHttpSoap11Endpoint"/>
</wsdl:port>
<wsdl:port name="ABSHttpSoap12Endpoint" binding="ns:ABSSoap12Binding">
<soap12:address location="
http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint"/>
</wsdl:port>
</wsdl:service> ............

Can anyone tell me why the location is like "
http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint". It should be
http://192.168.1.54:8080/services/ABS only.

Is there anything through which I can configure this behavior?

Chinmoy

RE: Different address location in WSDL generated by Axis2

Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hi Keith,
 
When the webservice client sends a request to the location
(serviceName.endpointName or
http://192.168.1.54:8080/services/serviceName.endPointNameHttpSoap11Endp
oint
<http://192.168.1.54:8080/services/serviceName.endPointNameHttpSoap11End
point> ) mentioned in the WSDL, the request fails. It works if the
request is sent to "http://192.168.1.54:8080/services/serviceName
<http://192.168.1.54:8080/services/serviceName.endPointNameHttpSoap11End
point> ".
 
Do we expect the client o strip out the endpointName before sending the
request?
 
Thanks,
JP
 
________________________________

From: keith chapman [mailto:keithgchapman@gmail.com] 
Sent: Tuesday, October 21, 2008 7:58 AM
To: axis-user@ws.apache.org
Subject: Re: Different address location in WSDL generated by Axis2


Hi,

Since Axis2 1.4 we have the concept of dispatching request to the
endpoints not just to the service. The reason is that security scenarios
could be configured on a endpoint level and hence we need to know the
exact endpoint a request is headed to in order to apply the security
scenario accordingly.

This is the reason you see the unique addresses for each endpoint and it
takes the form serviceName.endpointName.

Thanks,
Keith.


On Tue, Oct 21, 2008 at 7:44 PM, Chinmoy Chakraborty <cc...@gmail.com>
wrote:


	
	Hi All,
	 
	Following is my service portion of the WSDL of service ABS
generated by Axis2 1.4.
	....................
	<
	wsdl:service name="ABS"> 
	<wsdl:port name="ABSHttpSoap11Endpoint"
binding="ns:ABSSoap11Binding">
	<soap:address
location="http://192.168.1.54:8080/services/ABS.ABSHttpSoap11Endpoint"/>
	</wsdl:port>
	<wsdl:port name="ABSHttpSoap12Endpoint"
binding="ns:ABSSoap12Binding">
	<soap12:address
location="http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint"/>
	</wsdl:port>
	</wsdl:service> ............
	 
	Can anyone tell me why the location is like
"http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint". It should
be http://192.168.1.54:8080/services/ABS only.
	 
	Is there anything through which I can configure this behavior?
	 
	
	Chinmoy




-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

RE: Different address location in WSDL generated by Axis2

Posted by "Pugalia, Jai P (JP)" <jp...@avaya.com>.
Hmm...ignore my question :-)
 
The security constraint tag had a typo :-(
 
Thanks,
JP

________________________________

From: Pugalia, Jai P (JP) 
Sent: Sunday, November 09, 2008 4:09 PM
To: 'axis-user@ws.apache.org'
Subject: RE: Different address location in WSDL generated by Axis2


Hi Keith,
 
When the webservice client sends a request to the location
(serviceName.endpointName or
http://192.168.1.54:8080/services/serviceName.endPointNameHttpSoap11Endp
oint
<http://192.168.1.54:8080/services/serviceName.endPointNameHttpSoap11End
point> ) mentioned in the WSDL, the request fails. It works if the
request is sent to "http://192.168.1.54:8080/services/serviceName
<http://192.168.1.54:8080/services/serviceName.endPointNameHttpSoap11End
point> ".
 
Do we expect the client o strip out the endpointName before sending the
request?
 
Thanks,
JP
 
________________________________

From: keith chapman [mailto:keithgchapman@gmail.com] 
Sent: Tuesday, October 21, 2008 7:58 AM
To: axis-user@ws.apache.org
Subject: Re: Different address location in WSDL generated by Axis2


Hi,

Since Axis2 1.4 we have the concept of dispatching request to the
endpoints not just to the service. The reason is that security scenarios
could be configured on a endpoint level and hence we need to know the
exact endpoint a request is headed to in order to apply the security
scenario accordingly.

This is the reason you see the unique addresses for each endpoint and it
takes the form serviceName.endpointName.

Thanks,
Keith.


On Tue, Oct 21, 2008 at 7:44 PM, Chinmoy Chakraborty <cc...@gmail.com>
wrote:


	
	Hi All,
	 
	Following is my service portion of the WSDL of service ABS
generated by Axis2 1.4.
	....................
	<
	wsdl:service name="ABS"> 
	<wsdl:port name="ABSHttpSoap11Endpoint"
binding="ns:ABSSoap11Binding">
	<soap:address
location="http://192.168.1.54:8080/services/ABS.ABSHttpSoap11Endpoint"/>
	</wsdl:port>
	<wsdl:port name="ABSHttpSoap12Endpoint"
binding="ns:ABSSoap12Binding">
	<soap12:address
location="http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint"/>
	</wsdl:port>
	</wsdl:service> ............
	 
	Can anyone tell me why the location is like
"http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint". It should
be http://192.168.1.54:8080/services/ABS only.
	 
	Is there anything through which I can configure this behavior?
	 
	
	Chinmoy




-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: Different address location in WSDL generated by Axis2

Posted by keith chapman <ke...@gmail.com>.
Hi,

Since Axis2 1.4 we have the concept of dispatching request to the endpoints
not just to the service. The reason is that security scenarios could be
configured on a endpoint level and hence we need to know the exact endpoint
a request is headed to in order to apply the security scenario accordingly.

This is the reason you see the unique addresses for each endpoint and it
takes the form serviceName.endpointName.

Thanks,
Keith.

On Tue, Oct 21, 2008 at 7:44 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:

> Hi All,
>
> Following is my service portion of the WSDL of service ABS generated by
> Axis2 1.4.
> ....................
> <
> wsdl:service name="ABS"> <wsdl:port name="ABSHttpSoap11Endpoint" binding="
> ns:ABSSoap11Binding">
> <soap:address location="
> http://192.168.1.54:8080/services/ABS.ABSHttpSoap11Endpoint"/>
> </wsdl:port>
> <wsdl:port name="ABSHttpSoap12Endpoint" binding="ns:ABSSoap12Binding">
> <soap12:address location="
> http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint"/>
> </wsdl:port>
> </wsdl:service> ............
>
> Can anyone tell me why the location is like "
> http://192.168.1.54:8080/services/ABS.ABSHttpSoap12Endpoint". It should be
> http://192.168.1.54:8080/services/ABS only.
>
> Is there anything through which I can configure this behavior?
>
> Chinmoy
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org