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
