Ok I've found the issue after some careful examination of my wsdl.... The problem resides here:
Zamite wrote: > > > <wsdl:binding name="TestSoapBinding" type="TestPortType"> > <soap:binding style="rpc" > transport="http://schemas.xmlsoap.org/soap/http"/> > <wsdl:operation name="Test"> > <soap:operation soapAction="" style="document"> > <wsdl:input> > <soap:body > namespace="http://localhost:8080/ode/processes/Test.wsdl"; > use="literal"/> > </wsdl:input> > <wsdl:output> > <soap:body > namespace="http://localhost:8080/ode/processes/Test.wsdl"; > use="literal"/> > </wsdl:output> > </soap:operation> > </wsdl:operation> > </wsdl:binding> > > > <wsdl:service name="TestService"> > <wsdl:port name="TestPort" binding="TestSoapBinding"> > <soap:address > location="http://localhost:8080/ode/processes/Test"/> > </wsdl:port> > </wsdl:service> > > type="TestPortType" should be type="tns:TestPortType". binding="TestSoapBinding" should be binding="tns:TestSoapBinding". And wsdl:input and wsdl:output elements shouldn't be inside the soap:operation, but inside its parent -> wsdl:operation. Solving all these issues resulted in resolving the endpoint problem (which makes sense since it this clearly creates problems with binding to the operation's endpoints). -- View this message in context: http://old.nabble.com/Could-not-activate-endpoint-for-service-tp28165674p28229062.html Sent from the Apache Ode User mailing list archive at Nabble.com.
