Hi,
From the log, I can't see your cxf consumer start correctly, if you
consumer start correctly, the log should print out something like
May 7, 2008 11:53:08 AM org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server's publish address to be
http://localhost:8192/EchoService
Could you decribe how you package your SUs and SA? Any chance you append
the jbi.xml for your SA?
Freeman
Håkon Sagehaug wrote:
Hi,
See inline
2008/5/6 Freeman Fang <[EMAIL PROTECTED]>:
Hi,
The info
INFO - WSDL1Processor - EndpointServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>]has
a service description, but no matching endpoint found in
is print out when start cxf bc provider, this is normal when start cxf bc
provider which specify endpoint name is different with the port name in wsdl
and this info will not prevent you to see the wsdl from
http://0.0.0.0:8192/EchoService/?wsdl, since cxf consumer publish this
wsdl.
From your info I can't tell what's the problem with your consumer, could
you use some command like
netstat -nap|grep 8192
Here is the result of netstat -nap|grep 8192
tcp 0 0 :::8192 :::*
LISTEN 22734/java
to see if port 8192 is on of your localhost?
Or would you append you full log when deploy the SA
Here is what output I get when I deploy it
INFO - AutoDeploymentService - Directory: hotdeploy: Archive
changed: processing cxf-tutorial-sa-1.0-SNAPSHOT.jar ...
DEBUG - AutoDeploymentService - Unpacked archive
/Home/bccs/hakont/apache-servicemix-3.2.1/hotdeploy/cxf-tutorial-sa-1.0-SNAPSHOT.jar
to
/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/tmp/cxf-tutorial-sa-1.0-SNAPSHOT.0.tmp
DEBUG - SedaFlow - Called Flow suspend
DEBUG - JMSFlow - Called Flow suspend
DEBUG - JCAFlow - Called Flow suspend
DEBUG - AutoDeploymentService - SA dependencies:
[servicemix-cxf-bc]
DEBUG - DeploymentService - Moving
/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/tmp/cxf-tutorial-sa-1.0-SNAPSHOT.0.tmp
to
/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/install
DEBUG - DeploymentService - Unpack service unit archive
/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/install/tutorial-cxf-provider-su-1.0-SNAPSHOT.zip
to
/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/sus/servicemix-cxf-bc/tutorial-cxf-provider-su
DEBUG - CxfBcComponent - Deploying service unit
DEBUG - CxfBcComponent - Looking for
/Home/bccs/hakont/apache-servicemix-3.2.1/data/smx/service-assemblies/cxf-tutorial-sa/version_1/sus/servicemix-cxf-bc/tutorial-cxf-provider-su/xbean.xml:
true
DEBUG - CxfBcComponent - Service unit deployed
INFO - ServiceAssemblyLifeCycle - Starting service assembly:
cxf-tutorial-sa
INFO - ServiceUnitLifeCycle - Initializing service unit:
tutorial-cxf-provider-su
DEBUG - CxfBcComponent - Initializing service unit
DEBUG - CxfBcComponent - Service unit initialized
INFO - ServiceUnitLifeCycle - Starting service unit:
tutorial-cxf-provider-su
DEBUG - CxfBcComponent - Starting service unit
DEBUG - ComponentContextImpl - Component: servicemix-cxf-bc
activated endpoint: {http://www.bccs.uib.no/EchoService.wsdl}EchoService :
EchoServiceProxy
DEBUG - CxfBcComponent - Querying service description for
ServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy
]
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
[EchoServiceLocal]
DEBUG - CxfBcComponent - Querying service description for
ServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy
]
DEBUG - WSDL2Processor - Endpoint ServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy]
has a non WSDL2 service description
DEBUG - JCAFlow - ServiceMix: broadcasting info for
org.apache.servicemix.jbi.event.EndpointEvent[source=ServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy
]]
DEBUG - JMSFlow - ServiceMix: broadcasting info for
org.apache.servicemix.jbi.event.EndpointEvent[source=ServiceEndpoint[service={
http://www.bccs.uib.no/EchoService.wsdl}EchoService,endpoint=EchoServiceProxy
]]
DEBUG - CxfBcComponent - Service unit started
DEBUG - SedaFlow - Called Flow resume
DEBUG - JMSFlow - Called Flow resume
DEBUG - JCAFlow - Called Flow resume
INFO - AutoDeploymentService - Directory: hotdeploy: Finished
installation of archive: cxf-tutorial-sa-1.0-SNAPSHOT.jar
Thanks for the help, I've banged my head against the desk now for a couple
of hours
Freeman
Håkon Sagehaug wrote:
---------- Forwarded message ----------
From: Håkon Sagehaug <[EMAIL PROTECTED]>
Date: 2008/5/6
Subject: Re: Using cxf consumer and provider
To: [email protected]
hi
I got the same error, any other tips, I think I've also most tried
everything suggested in the lists.
cheers, Håkon
2008/5/6 Freeman Fang <[EMAIL PROTECTED]>:
Hi,
Add
endpoint="EchoService"
service="bccs:EchoService"
for your consumer, this should work
Freeman
Håkon Sagehaug wrote:
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<http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,endpoint=EchoServiceProxy>
<
http://www.bccs.uib.no/EchoService.wsdl%7DEchoService,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
yes, it's correct
cheers, Håkon
