Using cxf consumer and provider

[Håkon Sagehaug]

Hi

I've got a as it seems a known problem, looked at the mailing list, but have
not managed to solve my problem.

The setup is like this. I've got a external web service that I want to call
through service mix using cxf consumer and provider. I've got one cxf su
that contains a xbean.xml file like this

<beans xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0";
     xmlns:bccs="http://www.bccs.uib.no/EchoService.wsdl";

>

<cxfbc:consumer wsdl="classpath:service.wsdl"

                      targetEndpoint="EchoServiceProxy"
                      targetService="bccs:EchoService"
                      targetInterface="bccs:EchoServicePortType"/>

 <cxfbc:provider wsdl="classpath:service.wsdl"
                      locationURI="
http://localhost:8080/axis2/services/EchoService/";
                      endpoint="EchoServiceProxy"
                      service="bccs:EchoService"

interfaceName="bccs:EchoServicePortType"                      />

</beans>

And a wsdl file in the same folder like this

<?xml version="1.0" encoding="UTF-8"?>
<definitions name="EchoService" targetNamespace="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns="
http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema"; xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/";>
  <types>
    <xsd:schema elementFormDefault="qualified" targetNamespace="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns:tns="
http://www.bccs.uib.no/EchoService.wsdl"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema";>
            <xsd:element name="SayHi">
                <xsd:complexType>
                    <xsd:sequence>
                        <xsd:element name="Hi" type="xsd:string"/>
                    </xsd:sequence>
                </xsd:complexType>
            </xsd:element>
            <xsd:element name="SayHiResponse">
                <xsd:complexType>
                    <xsd:sequence>
                        <xsd:element name="HiResponse" type="xsd:string"/>
                    </xsd:sequence>
                </xsd:complexType>
            </xsd:element>
        </xsd:schema>
  </types>
  <message name="SayHiRequestMsg">
    <part name="parameters" element="tns:SayHi">
    </part>
  </message>
  <message name="SayHiResponseMsg">
    <part name="parameters" element="tns:SayHiResponse">
    </part>
  </message>
  <portType name="EchoServicePortType">
    <operation name="SayHi">
<documentation>Just a simple echo operation that returns the same string
that is given to it.</documentation>
      <input message="tns:SayHiRequestMsg">
    </input>
      <output message="tns:SayHiResponseMsg">
    </output>
    </operation>
  </portType>
  <binding name="EchoServiceBinding" type="tns:EchoServicePortType">
    <soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"/>
    <operation name="SayHi">
      <soap:operation soapAction="
http://www.bccs.uib.no/EchoService.wsdl/SayHi"/>
      <input>
        <soap:body use="literal"/>
      </input>
      <output>
        <soap:body use="literal"/>
      </output>
    </operation>
  </binding>
  <service name="EchoService">
<documentation>This WSDL file describes a simple Echo Service that echoes a
string sendt to it. This service is intended primarily for testing
purposes.</documentation>
    <port name="EchoService" binding="tns:EchoServiceBinding">
      <soap:address location="http://0.0.0.0:8192/EchoService"/>
    </port>
  </service>
</definitions>

But when I deploy the service assembly  get this

INFO  - WSDL1Processor                 - Endpoint ServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy]
has a service description, but no matching endpoint found in [EchoService]

and when I go to http://0.0.0.0:8192/EchoService/?wsdl i don't get any wsdl,
just HttpError:404

I'm sure the error is easy to fix, but have not been able to solve it, any
tips out there??

Also the location of the ws in the wsdl is on servicemix port, this is
correct right, and in the provider the locationURI will overwrite this value
and send it to the appropriate

cheers, Håkon




-- 
Håkon Sagehaug, Software Developer
Parallab, Bergen Center for Computational Science (BCCS)
UNIFOB AS (University of Bergen Research Company)