Expose xfire services using interfaces, rather than the implementation.

I saw this issue friday and gave it a thought. unfortunately on friday I could not download the patch created by Eric so I had to find my way on how to do this, which luckily I managed.

My idea behind this was to configure the interface used to expose the method by adding a method to the component, like this one:

<mule-descriptor name="HelloWorld" implementation="com.ricston.components.HelloWorld">
<inbound-router>
<endpoint address="xfire:http://localhost:82/services"/>
</inbound-router>
<properties>
<property name="exposedInterface" value="com.ricston.components.IHelloWorld"/>
</properties>
</mule-descriptor>

and eventually, in the XFireMessageReceiver class you create the class to expose occordingly

should i submit this new feature?

committed.

Services will need to be configured as follows:
<mule-descriptor name="HelloWorld" implementation="com.ricston.components.HelloWorld">
<inbound-router>
<endpoint address="xfire:http://localhost:82/services"/>
</inbound-router>
<properties>
<list name="serviceInterfaces">
<entry value="com.ricston.components.IHelloWorld3"/>
</list>
</properties>
</mule-descriptor>

Although it is a list of "serviceInterfaces", XFireMessageReceive will only consider the first one in the list. It is implemented as a list to be in exactly the same way as axis is configured.

if there is more than one interface which you need to expose, the work around is simple, create an abstract class inherits from both you interfaces, and as serviceInterfaces add this class.

I will update the wiki soon.

doc updated:
http://mule.mulesource.org/wiki/display/MULE/XFire

under heading: Exposing methods using Interfaces/Abstract Classes...