Not necessarily, We can pickup the ORB component for test dependency on
other apache project where it will go from yoko.
-- Ulhas Bhole
James Mao wrote:
But we should also do the interop test as well if we migrate it from
YOKO, right?
With Orbix?
James
Well, by CORBA, I really mean IIOP, but that's a detail.
Basically, it's a combination binding (like soap) + transport (http)
where the JAXB (for example) objects get mashalled down to corba
streamables (instead of soap) and send on the wire via the IIOP stuff.
The tooling is basically tools to do things like:
idl -> wsdl
wsdl -> idl
wsdl -> "wsdl with corba binding defined"
etc...
Dan
On Friday 30 November 2007, Glen Mazza wrote:
Just to make sure I understand this correctly, when you mean "corba
binding", you mean another transport, just like HTTP or JMS, correct?
Thanks,
Glen
Am Freitag, den 30.11.2007, 16:27 -0500 schrieb Daniel Kulp:
I just want to go on record as saying I COMPLETELY support this and
think the CXF parts of this makes a lot of sense for the CXF
project. I've always felt the binding parts of Yoko should have
been done in CXF to start off with.
For those that aren't familliar with it, the yoko ws binding stuff
described in the proposal provides some tooling and a corba binding
for CXF. It allows a CXF client (like a JAX-WS/JAXB client, but
should work with the other frontends) to talk to CORBA servers or
for a CXF server to be exposed as a CORBA server so other CORBA apps
can talk to it.
Anyway, Matt wants a vote to accept the proposal or not, but I'd
like to leave this open for discussion for a couple days first as
I'd like to hear others thoughts about it.
Dan
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
