at the bottom of the wsdl you have a description of the service and Port
<service name="ICBDPChannel_Service">
<port binding="tns:ICBDPChannelSoapBindingHTTP" name="ICBDPChannelPortHTTP">
<soap:address
location="http://localhost:8080/axis/services/webservices.ICBDPChannelSoapBindingHTTP"/>
</port>
</service>
anyone landing on
http://localhost:8080/axis/services/webservices.ICBDPChannelSoapBindingHTTP"/>
<wsdl:service name="Version"> <wsdl:port name="VersionHttpSoap11Endpoint"
binding="ns:VersionSoap11Binding"> <soap:address
location="http://localhost:8007/axis2/services/Version.VersionHttpSoap11Endpoint/"/></wsdl:port>
<wsdl:port name="VersionHttpSoap12Endpoint"
binding="ns:VersionSoap12Binding"> <soap12:address
location="http://localhost:8007/axis2/services/Version.VersionHttpSoap12Endpoint/"/>
</wsdl:port> <wsdl:port name="VersionHttpEndpoint"
binding="ns:VersionHttpBinding"> <http:address
location="http://localhost:8007/axis2/services/Version.VersionHttpEndpoint/"/>
</wsdl:port></wsdl:service> endpoiint
http://localhost:8007/axis2/services/Version.VersionHttpSoap11Endpointreferences
service-name="Version" and Port Name=VersionHttpSoap11Endpoint
invalid Operations are usually caused by fubar'ed InputMessage, OutputMessage
and FaultMessage
if you post the wsdl we can diagnose for you Viel Gluck!
Martin
______________________________________________
Porfavor..no altere esta communicacion..Gracias > Date: Thu, 8 Dec 2011
13:21:32 -0800
> From: rexclaim...@yahoo.com
> Subject: Endpoint/Operation not found
> To: java-user@axis.apache.org
>
> I've been struggling with the dreaded "The endpoint reference (EPR) for the
> Operation not found..." error for over a day. I've read Keith Chapman's blog
> post
> (http://www.keith-chapman.org/2009/02/axis2-endpoint-reference-epr-for.html),
> used TCPMon and debugged and still don't know why the operation is not found.
>
> I have 3 other operations in the service that are working fine so the
> endpoint does not appear to be the problem. In debug I stepped into the
> AxisBasedOperationDispatcher#findOperation method. The action comes back
> correctly from the #messageContext.getSoapAction() method call. Then I step
> into the #getOperationBySOAPAction method. This returns null. I noticed
> that the operation was in the invalidOperationAliases List object. This may
> be the issue. Why would it be in this List?
>
> Any help is appreciated.
>
> Thanks,
> J
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>
