Aegis cannot read WSDL or XML schema. All it can do is derive a schema from code. It can produce WSDL and XML schema.
Thus, one safe configuration is: - Aegis server - Some Other Client that is configured using the WSDL/schema from Aegis. Another safe configuration is: - Aegis server - Aegis client - Exactly the same Java code for the interfaces and data objects in each. - Exactly the same version of CXF in each. (We try to keep it compatible, but ...) On the other hand, something that's unlikely to work is: - Some Other Server - Aegis Client because there's approximately no chance that the Aegis client will happen to derive the same Java<->XML mapping as the server. On Sat, Mar 19, 2011 at 3:49 AM, Raj Floyd <[email protected]> wrote: > Hi, > > I read the following line in the Aegis documentation and need to understand > a bit. > > "it's not all that practical to use Aegis as a client to talk to some a > service using some other data binding" > > Does it mean that Aegis will work with 'Aegis enabled CXF client' and > 'non-Aegis CXF service' > But it will not work with 'Aegis enabled CXF client' and 'non-Aegis non-CXF > service' > > Please clarify. > > Thx > > Raj >
