Anyone familiar with calling a remote XFire service and using Aegis
binding from Mule(client) to handle the XML/Java binding. Do I need the
services.xml file within the client(Mule) as well? I have the
<classname>.aegis.xml files on the Mule side, but this doesn't seem to
allow me to handle everrything correctly. Specicifally inheritance.
s.xml
I have the following entries within the remote XFire service definition:
<properties>
<!--
This list specifies all the sub-classes of
types used in the service.
In order for these sub-classes to be
included in the generated WSDL
they must be included in the list below.
e.g. The service method
loadGelcoCCAddendum(GelcoCCAddendum gelcoCCAddendum);
takes an abstract GelcoCCAddendum, but
really this could take any
sub-classes of GelcoCCAddendum e.g.
GelcoLodgingCCAddendum.
-->
<property key="writeXsiType">true</property>
<property key="overrideTypesList">
<list xmlns="">
<value>
gelco.messaging.v1.creditcard.GelcoCCTransaction</value>
<value>
gelco.messaging.v1.creditcard.GelcoCCAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoLodgingCCAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoRentalCCAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoTravelCCAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoCCItemizationAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoLodgingCCItemizationAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoRentalCCItemizationAddendum</value>
<value>
gelco.messaging.v1.creditcard.GelcoTravelCCItemizationAddendum</value>
</list>
</property>
</properties>
Do I need these entries on the client side as well? If so, what it the
best way yo do this?
Thanks!
Bob
