axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From keith chapman <>
Subject Re: Does HTTPEndpointStub work?
Date Wed, 18 Mar 2009 07:28:16 GMT
Could you post your wsdl please?


On Tue, Mar 17, 2009 at 8:35 PM, jcaristi <> 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:
> Sent from the Axis - User mailing list archive at

Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.


View raw message