SHORB

SHORB allows the remote access to Java Objects over HTTP.

SHORB is designed to simplify the remote objects management and to provide an easily scalable and secure remote Method Invocations service Architecture encapsulating the user from the Remote Objects references management.

The objects live in the Openode Orb Containers, a kind of Objects Database. This element provides the basic operations to create, delete, keep, search and execute object’s methods.

SHORB is instanced in the context of an HTTP Server supporting Servlets. The access to the service is done over HTTP.

The principal benefits of using SHORB is its simplicity: once you have an object instanced in the SHORB registry its access is very simple, which can be done in two different ways: a basic Reflect based access and a Stub based one.

The Basic access is done by looking up the remote object and obtaining a Remote Reference of type IRORef.

IRORef is defined as the following Interface which offers all the necessary to interact with the Remote Object:

package org.openode.shorb.naming;

import java.rmi.RemoteException;

public interface IRORef extends java.io.Serializable{
public Object exec(String m, Object[] p) throws RemoteException;
public IRORef execRef(String m, Object[] p) throws RemoteException;
public void delete() throws RemoteException;
public String getPath() throws RemoteException;
public String getName() throws RemoteException;
public String getOrbId() throws RemoteException;
public IRORef export(String naming, String url) throws RemoteException;

}

The second approach implicates the use or the org.openode.shorb.remote.rmic tool which generates the Stub for a concrete Interface. The advantadge in here is that the rmic tool acts over Interfaces and not over classes. In fact it is not mandatory for the remote object accessed through the stub to implement the Interface.