Yes, it's working, I copy the contents of xfire.xml into servicemix.xml and now Servicemix runs without complaint.

Altough I must have screwed something else because the response of the service for this request:

<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
 <env:Body>
   <m:echo xmlns:m='http://xfire.components.servicemix.org'>
     <m:in0> Yo Yo </m:in0>
   </m:echo>
 </env:Body>
</env:Envelope>

   is:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
 <soap:Body>
   <soap:Fault>
     <faultcode>Server</faultcode>
<faultstring>Parameter {http://xfire.components.servicemix.org}in0 does not exist!</faultstring>
   </soap:Fault>
 </soap:Body>
</soap:Envelope>

   I'll keep looking.

   Thank's.

Matthew Parrish wrote:

Yes, it is hard to know exactly what to do.  Include this spring file in
your spring context.  It is from the xfire-spring.jar

classpath:org/codehaus/xfire/spring/xfire.xml
-----Original Message-----
From: Angel Gomez [mailto:[EMAIL PROTECTED] Sent: Thursday, August 18, 2005 2:01 PM
To: servicemix
Subject: [servicemix-user] Errors in xfire echo example


   Hi.

   I have been trying to run the xfire echo example and found this:

<!-- The Service Bean -->

 <bean id="echo" class="org.servicemix.components.xfire.Echo"
singleton="true"/>

 <bean name="Echo" class="org.codehaus.xfire.spring.ServiceComponent">
   <property name="service" ref="*xfireReceiverService*"/>
   <property name="serviceFactory" ref="*xfire.serviceFactory*"/>
   <property name="xfire" ref="xfire"/>
 </bean>

        I think that the "service" ref should be "echo" as in the *id* of
the first bean definition.

        For the "serviceFactory", the servicemix throws an error stating a
NoSuchBeanDefinitionException, no bean named 'xfire.serviceFactory' is
defined. I have not been able to fix this last error, I have gone thru the
examples and test either on cvs and the wiki but have not found were or how
this bean is defined.

        Regards.


Reply via email to