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 jcaristi <jc...@whisolutions.com> on 2009/03/17 16:05:26 UTC
Does HTTPEndpointStub work?
I am generating ADB stubs from hand-coded WSDL, for an Axis2 service that is
embedded in a web application. I have both SOAP and HTTP endpoints defined.
I can successfully call my web service using both SOAP and REST clients.
SoapUI works for both. The HttpSoap11EndpointStub works for both (using the
ENABLE_REST option for REST). I have also created a Service client that
works.
What does not work is the HTTPEndpointStub, and I'm not sure why, or even if
I need it. I do want to support both SOAP and REST. I would like to use the
most efficient approach, which is why I am asking these questions.
The working URL (in all the above scenarios) for my service is:
/partselect/services/PartSelectService/
When I attempt to use the HTTPEndpointStub, its URL is different. I get the
error:
The service cannot be found for the endpoint reference (EPR) /partselect/
services/PartSelectService.PartSelectServiceHttpEndpoint/PartSelectService/MakeSearch
Why is an HTTPEndpointStub created? Why does this stub create the URL in
this way? How does one configure the server to listen on this type of
endpoint? Should I just use the HTTPSoap11EndpointStub, or should I try to
get this one working?
--
View this message in context: http://www.nabble.com/Does-HTTPEndpointStub-work--tp22561063p22561063.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Does HTTPEndpointStub work?
Posted by jcaristi <jc...@whisolutions.com>.
Here it is:
http://www.nabble.com/file/p22577300/PartSelectService.wsdl
PartSelectService.wsdl
Keithgchapman wrote:
>
> Could you post your wsdl please?
>
> Thanks,
> Keith.
>
>
--
View this message in context: http://www.nabble.com/Does-HTTPEndpointStub-work--tp22561063p22577300.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Does HTTPEndpointStub work?
Posted by keith chapman <ke...@gmail.com>.
Could you post your wsdl please?
Thanks,
Keith.
On Tue, Mar 17, 2009 at 8:35 PM, jcaristi <jc...@whisolutions.com> wrote:
>
> I am generating ADB stubs from hand-coded WSDL, for an Axis2 service that
> is
> embedded in a web application. I have both SOAP and HTTP endpoints
> defined.
> I can successfully call my web service using both SOAP and REST clients.
> SoapUI works for both. The HttpSoap11EndpointStub works for both (using
> the
> ENABLE_REST option for REST). I have also created a Service client that
> works.
>
> What does not work is the HTTPEndpointStub, and I'm not sure why, or even
> if
> I need it. I do want to support both SOAP and REST. I would like to use
> the
> most efficient approach, which is why I am asking these questions.
>
> The working URL (in all the above scenarios) for my service is:
>
> /partselect/services/PartSelectService/
>
> When I attempt to use the HTTPEndpointStub, its URL is different. I get
> the
> error:
>
> The service cannot be found for the endpoint reference (EPR) /partselect/
>
> services/PartSelectService.PartSelectServiceHttpEndpoint/PartSelectService/MakeSearch
>
> Why is an HTTPEndpointStub created? Why does this stub create the URL in
> this way? How does one configure the server to listen on this type of
> endpoint? Should I just use the HTTPSoap11EndpointStub, or should I try to
> get this one working?
>
>
> --
> View this message in context:
> http://www.nabble.com/Does-HTTPEndpointStub-work--tp22561063p22561063.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org