EJOE is a lightweight Java remoting framework built to send and receive objects through pluggable (de)serialization mechanisms. It offers a high-performance, simple, and clean object request broker (whereby ORB is meant in its natural manner and not in its relation with CORBA), with server and client components for your client/server applications. It's a highly scalable implementation of the common request-process-response pattern based on Java NIO. It does support optional remote class loading to avoid redundant classpath entries, but doesn't require stubs and/or proxy objects.
|Tags||Software Development Libraries Java Libraries Object Brokering|
|Operating Systems||OS Independent|
Release Notes: Just a maintenance release containing some minor bugfixes and updated dependencies. Some incompatibilities with Java 5 as well as a java.lang.ClassCastException when activating remote classloading in EJServer were fixed.
Release Notes: There are many bugfixes, and many new features were added. Remote reflection, different serialization strategies, support for the concurrency package of Java 5, Crispy and WSIF extensions, partial HTTP support, and support for interprocess communication within the same Java virtual machine are the most important improvements. It is considered stable and ready for use in production environments.
Release Notes: Some minor bugs and the broken gzip compression were fixed. New adapters for XMLBeans and JSON Tools were added. This release contains a factory for dynamic proxy classes and a caching mechanism for native ByteBuffer objects.
Release Notes: This is the first milestone of the upcoming 0.4.0 release. Beside many bugfixes, a lot of new features were added. Remote reflection, different serialization strategies, support for the concurrency package of Java 5, crispy and wsif extensions, and partial HTTP support are just the most important improvements of this release.
Release Notes: Two critical bugs have been fixed: A critical, time consuming lock occurred on some systems. The server component doesn't require applications to offer an application loop to avoid termination by reaching the end of the code. This version also contains some enhancements originally planned for the next major release, and is most likely the most efficient version to date.