incubator-yoko-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Petrenko" <alexey.a.petre...@gmail.com>
Subject Re: [general] 100% 1.5 API coverage for Harmony and CORBA.
Date Thu, 11 Jan 2007 16:12:01 GMT
I've attached an html file with the full list of differences to the
original message.
Examples....
class org.omg.CORBA.ACTIVITY_COMPLETED: missing in harmony.org.omg
class org.omg.CORBA.ACTIVITY_REQUIRED: missing in harmony.org.omg
class org.omg.CORBA.FieldNameHelper: missing in harmony.org.omg
class org.omg.CORBA.INVALID_ACTIVITY: missing in harmony.org.omg
class org.omg.CORBA.NameValuePair: missing in harmony.org.omg
class org.omg.CORBA.NameValuePairHelper: missing in harmony.org.omg

Some of the classes exists in Yoko but has different names.

SY, Alexey


2007/1/11, David Jencks <david_jencks@yahoo.com>:
> I wonder if someone could give an example of one of these classes and
> methods that disappeared moving from corba 2.3 to 2.4?  Is there
> something equivalent but named differently in 2.4?
>
> thanks
> david jencks
>
> On Jan 11, 2007, at 10:19 AM, Alexey Petrenko wrote:
>
> > This is mainly a Harmony issue but I've also added yoko-dev list since
> > it connected to Yoko and probably Yoko community will give us a good
> > advice.
> >
> > As you know we got 100% Java 5 SE coverage target for Q1 2007 [1]. It
> > is Q1 2007 now...
> >
> > One of the areas with less then 100% coverage in Harmony is org.omg
> > packages. I've attached the japitools result page with the current
> > Harmony status in this area. The summary is the following: 84.52%. To
> > get 100% we need to fix 6 classes, 28 interfaces, 11 methods and
> > implement 2 packages, 21 classes, 12 interfaces, 72 methods, 2
> > constructors.
> >
> > There are two main causes of such situation:
> > 1. Yoko implements CORBA 2.4 while Java 5 SE implements 2.3
> > 2. There is no any spec for CORBA implementation on Java.
> >
> > We can not ask Yoko community to downgrade CORBA version to 2.3
> > because this will be impolite and very strange request :)
> >
> > So I suggest to create a new corba module in Harmony and implement
> > missed classes and packages on top of Yoko. Probably some of Yoko guys
> > will help Harmony...
> >
> > It is not so simple situation with "bad" classes and "missed" methods
> > because these changes requires source modification. Some changes could
> > be acceptable for Yoko but definitely not all of them.
> > For unacceptable changes we can put copy of the class source to
> > Harmony repository and change it there. And we should not forget to
> > merge updates from Yoko sometimes...
> >
> > Thoughts?
> >
> > SY, Alexey
> >
> > [1] http://harmony.apache.org/roadmap.html
>
>

Mime
View raw message