incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Piper <>
Subject Re: [compatibility] Do we want to be Java5 compatible?
Date Fri, 24 Nov 2006 16:42:04 GMT
FWIW the various versions are not completely compatible. For instance 
2.5 introduced an incompatible change in wstring marshalling that was 
corrected in 2.6. So which version you pick _does_ matter. 2.3 is a 
pain because it doesn't specify certain things particularly 
rigorously and different vendors did different things.

If it was me I would implement the 2.6 versions of the required parts 
of 2.3, since there is general agreement on marshalling etc, but I 
understand that implementing the whole of 2.6 is a pain since it 
introduces a bunch of stuff (such as PI) which you may not want to implement.

Note that the Sun ORB in J2SE 1.4+ implements _more_ than 2.3. In 
particular it implements Portable Interceptors (which were introduced 
in 2.4) + a bunch of other minor things.


At 16:19 24/11/2006, Geir Magnusson Jr. wrote:

>Alexey Petrenko wrote:
>>2006/11/24, Geir Magnusson Jr. <>:
>>>Alexey Petrenko wrote:
>>> > 2006/11/24, Geir Magnusson Jr. <>:
>>> >> Alexey Petrenko wrote:
>>> >> > 2006/11/23, Geir Magnusson Jr. <>:
>>> >> >> Alexey Petrenko wrote:
>>> >> >> > Do we want to be Java5 compatible?
>>> >> >> >
>>> >> >> > Yes, I understand that Yoko is CORBA 2.4 while Java5 and
even 6 are
>>> >> >> > CORBA 2.3. This means that it is impossible to create
>>> >> compatible
>>> >> >> > version since it will require downgrading Yoko and this
is not a
>>> >> >> > choice.
>>> >> >> Why is that true?
>>> >> >> Does CORBA 2.4 not include a complete CORBA 2.3?
>>> >> > Fully compatible means "both directions" for me.
>>> >> I don't understand what that means.
>>> > Both directions compatibility means that every program designed for
>>> > Java5 can be executed on Yoko and every program designed for Yoko can
>>> > be executed on Java5.
>>>But Harmony can't commit to such support - we are implementing a
>>>specific API (Java 5), and Yoko is free to do what it wants to...
>>That's why I said that it is impossible to make Yoko fully compatible
>>with Java5 in my first email. And nobody wants to. And nobody asks to.
>sorry - I feel like we're going in circles here.  I don't understand...
>Why can't yoko implement CORBA 2.3 completely (if that is our 
>requirement for JDK 5)?
>The TCK for SE 5 probably wont' care of there's *more* CORBA in 
>there, so the 2.4 things, if compatible with 2.3, should be fine.

Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

View raw message