Alexey Petrenko wrote:
If not then I got few questions/suggestions...
1. Which of the jars produced by Yoko build are more suitable for our
needs? I'm looking on yoko-core...
In addition you would probably want the yoko-rmi module, which
implements the stuff in javax.rmi and javax.rmi.CORBA .
In addition you would probably want an IDL compiler. Work on this has
not started yet.
2. I've compared CORBA from the Java2SE 5 with the Yoko Core (result
file is attached). The result summary is the following: "Success rate
is 77.6%. Bad: 112 classes, 50 interfaces, 576 methods. Missing: 3
packages, 21 classes, 13 interfaces, 37 methods, 2 constructors.
Abs.add: 2 methods."
Is it possible to set Java2SE 5 compatibility as a goal for the Yoko
subset implementing the Java2SE functionality? If so I can open JIRA
issues and prepare some patches corresponding to comparison failures.
Sounds excellent!
3. Yoko has more packages in org.omg then specified in 1.5 spec. Is it
possible to produce a special jar for Harmony without those packages?
:)
As I understand it, the 1.5 spec requires CORBA version 2.3.1 + a few
additions from later releases. Yoko implements CORBA version 2.4 (i
think). It is currently not possible to run Yoko using version 2.3 of
the CORBA spec.
Would it be OK (from a Harmony standpoint) to provide a higher level of
CORBA support than the spec requires? Provided, of course, that it is
fully backwards compatible?
4. Are you planing to put some prebuilt jars to your site? M1 release
for example... We think that the best way for us will be to download a
prebuilt Yoko jar and put it into our deploy directory.
A M1 milestone is on the way.
Does Harmony have any requirements regarding the dependencies we add to
yoko? For example, the yoko-rmi module currently requires apache BCEL.
Regards,
Anders
