Enterprise Object Broker (EOB) is an application server that transparently distributes Java objects via their interfaces. It makes no distinction between Local and Remote objects. Because of these features, it is not J2EE compliant. The developer builds beans that implement normal Java interfaces and the deployer decides where the beans are in a cluster of servers. Apache's AltRMI is used in place of RMI. It publishes plain interfaces locally and remotely. The interfaces do not have to extend the java.rmi.Remote interface. Methods do not have to throw RemoteException. AltRMI delivers remoting for Java. EOB sits on top of Apache's Avalon-Phoenix server platform.
|Tags||Software Development Object Brokering|
|Operating Systems||OS Independent|
Release Notes: Phoenix was updated to 4.0.4, Jetty to 4.2.9, AltRMI to 0.9.3, JSX to 22.214.171.124, and Phoenix to 4.0.4. The program now works with JDK 1.3.1 again. SimpleStore was replaced with Hibernate.
Release Notes: Jetty was updated to 4.2.7 and AltRMI to 0.9.1.
Release Notes: In this release, Phoenix was upgraded to 4.0.3, AltRMI was upgraded to 0.8, and Jetty replaces Jo! for Servlet 2.3 capability.
Release Notes: Proxies are now generated using the Byte Code Engineering Library (BCEL) instead of javac. Examples are now distributed separately in source form, as well as installable .eob (like .ear) files. These examples have been made easier to study and build.
Release Notes: EOB now supports .eob files. These are like .ear files for EJB in that they contain beans in jars and war files.