Generated by GPT-5-mini| JacORB | |
|---|---|
| Name | JacORB |
| Developer | ObjectWeb, Apache Software Foundation contributors |
| Released | 1999 |
| Programming language | Java |
| Platform | Java Virtual Machine |
| License | LGPL, Apache License (components) |
JacORB JacORB is a Java-based implementation of the CORBA specification designed to support distributed computing for enterprise and research applications. It originated in the late 1990s and has been developed by contributors from projects such as ObjectWeb, Apache Software Foundation, Eclipse Foundation, IBM, and Oracle Corporation, with use in academic environments like University of Cambridge and industry adopters including Fujitsu, Nokia, and Siemens.
JacORB implements the CORBA standard originally defined by the Object Management Group and complements other middleware such as TAO (The ACE ORB), ORBacus, MICO, and OpenORB. It targets interoperability with vendors like BEA Systems, Sun Microsystems, Microsoft, and Red Hat through adherence to standards including IIOP, GIOP, and OMG IDL. Its ecosystem overlaps with standards organizations and consortia such as W3C, IEEE, and ISO, and it has been compared in academic benchmarks alongside middleware like ICE (Internet Communications Engine) and ZeroC.
JacORB's architecture separates object request brokering, servant management, and transport layering, following design patterns used by Apache MINA, Netty, and JBoss projects. Core components map to modules familiar to developers from Spring Framework, Hibernate, and Apache Tomcat: an ORB core, POA-like lifecycles, stub/skeleton generation, and naming services interoperable with CORBA Naming Service and alternatives such as DNS and LDAP. For configuration and extension it uses mechanisms similar to OSGi bundles and integrates with build tools like Apache Maven and Apache Ant.
JacORB provides features expected in mature ORBs: IDL-to-Java mapping comparable to GNU Compiler Collection frontend behavior, dynamic invocation similar to Java Reflection, and interoperability with legacy systems maintained by Siemens AG and AT&T. It supports transactions and persistence via patterns aligned with Java Transaction API and can interwork with message brokers like Apache ActiveMQ, RabbitMQ, and IBM MQ. Additional capabilities include SSL/TLS transport with ciphers used in OpenSSL, security integration reflecting Java Authentication and Authorization Service approaches, and tools for debugging and monitoring akin to JConsole and VisualVM.
Implemented in Java Platform, Standard Edition, JacORB's source management has historically used repositories and workflows similar to GitHub, SourceForge, and Apache Subversion. Contributors have included engineers associated with Sun Microsystems, Oracle Corporation, Red Hat, Fujitsu Limited, and academic groups from University of Oxford and Massachusetts Institute of Technology. Development practice references patterns from Extreme Programming, Test-Driven Development, and CI systems like Jenkins and Travis CI. Packaging and distribution follow conventions used by Debian, Red Hat Enterprise Linux, and Ubuntu maintainers.
JacORB has been integrated into systems alongside application servers such as JBoss, WebLogic Server, and Apache Geronimo, and interoperate with web technologies like Apache HTTP Server, Nginx, and Jetty. It is used in domains where enterprises like Siemens, Thales Group, Airbus, and Bosch manage distributed object systems, and it has appeared in projects collaborating with institutions like NASA, European Space Agency, and CERN. Integrations often pair JacORB with frameworks such as Spring Framework, Jakarta EE, Eclipse RCP, and build ecosystems like Maven Central and Gradle.
Performance characteristics have been evaluated in studies alongside ORBs like TAO, ORBexpress, and ORBacus, measuring metrics influenced by JVM implementations from Oracle JDK, OpenJDK, and IBM J9 VM. Tuning leverages garbage collection strategies popularized by G1 GC and Z Garbage Collector and benefits from JVM profiling with YourKit and JProfiler. Security considerations address CVE advisories tracked by National Institute of Standards and Technology feeds and incorporate practices from OWASP, TLS guidance from IETF, and certificate management workflows used by Let's Encrypt and DigiCert. Common mitigations reference access control models seen in LDAP and federated identity approaches used by SAML and OAuth 2.0.
Category:Middleware