Geronimo
Geronimo uses the orb to implement the j2ee CORBA EJB binding support. Most of this support is done using POAs and Portable interceptors, so is fairly implementation neutral. However, to implement Geronimo's CSIv2 security, Geronimo needs to have some level of control over the transport-level security. In particular:
- requires ability to configure server listeners to use an appropriately configured SSL socket.
- requires ability to create an SSL socket for client connections when required by the IOR.
- requires hooks to control creation of the SSL Sockets so that keystores and truststores can be managed by server facilities.
- requires a transient name service. If possible, this should be capable of running in-process with other ORB instances.
- Frequently, multiple ORB instances will be required, both as client ORBs and server ORBs.
Harmony
Harmony requires an ORB to fulfil part of it's goal to implement the JSE 5.0 APIs. As such Harmony requires that Yoko does not use any implementation-specifc types or dependencies (i.e. no use of sun.io.CharToByteConverter etc. and no assumptions of unspecified behavior like hash values) so that it will run on any compliant JRE.
In addition incorporating OSGi metadata into the Yoko JARs would be helpful since the data are used in a common Harmony development scenario, and hopefully in the future runtime. If Yoko put the metadata in then Harmony would not have to repackage it.