Page History

...

• #Geronimo configuration
  • #Adjust {{config.xml}} to use Harmony RMI Registry provider for JNDI
  • #Customize the server startup
  • #Configure Deployer to use Harmony RMI Registry provider for JNDI
• #Harmony configuration
  • #Use DRLVM

Geronimo configuration

...

Use Harmony RMI Registry provider for JNDI

Harmony places JNDI providers in org.apache.harmony.jndi package tree, not in com.sun.jndi like Sun Java does, so you have to point Geronimo into the right direction to locate and properly access the RMI Registry provider.

...

<gbean name="NamingProperties">
  <attribute name="namingFactoryInitial">org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory</attribute>
  <attribute name="namingFactoryUrlPkgs">org.apache.harmony.jndi.provider</attribute>
  <attribute name="namingProviderUrl">rmi://${ServerHostname}:${NamingPort + PortOffset}</attribute>
</gbean>

Use TLS instead of SSL

Harmony doesn't have SSL implementation, so the following statements have to be added to var/config/config.xml file to instruct Geronimo to use TLS instead of SSL:

<module name="org.apache.geronimo.configs/j2ee-corba-yoko/2.0.2/car">
  <gbean name="CORBASSLConfig">
    <attribute name="protocol">TLS</attribute>
  </gbean>
</module>

Customize the server startup

...