You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Raj Floyd <ra...@gmail.com> on 2011/03/19 08:49:22 UTC
Aegis: Client and server
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
Re: Aegis: Client and server
Posted by Raj Floyd <ra...@gmail.com>.
Hi Benson,
Trying to understand further. Find my replies below.
On Sat, Mar 19, 2011 at 7:03 PM, Benson Margulies <bi...@gmail.com>wrote:
> Aegis cannot read WSDL or XML schema. All it can do is derive a schema
> from code. It can produce WSDL and XML schema.
>
OK
>
> Thus, one safe configuration is:
> - Aegis server
> - Some Other Client that is configured using the WSDL/schema from Aegis.
>
It means using Aegis, we produce WSDL/schema and using the same we
produce client code. Correct me if I am wrong.
>
> 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 ...)
>
I ran the Aegis sample by disabling Aegis on the server side. Still it
worked. So I conclude that becoz it had same interfaces and version on both
the sides and therefore it worked. Everything was CXF.
>
> On the other hand, something that's unlikely to work is:
> - Some Other Server
> - Aegis Client
>
You mean non-CXF server?
>
> because there's approximately no chance that the Aegis client will
> happen to derive the same Java<->XML mapping as the server.
> It means Aegis client will marshall it properly but server will not be able
> to unmarshall. Correct me if I am wrong.
>
>
> On Sat, Mar 19, 2011 at 3:49 AM, Raj Floyd <ra...@gmail.com> 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
> >
>
Re: Aegis: Client and server
Posted by Benson Margulies <bi...@gmail.com>.
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 <ra...@gmail.com> 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
>