"The Java ORB"

For many years now OCI has been providing high quality, commercial support for this highly regarded Java CORBA implementation. Many clients are finding that the multi language, multi platform approach of CORBA is the only way to build standards-based, open, integrated systems that will accommodate whatever the future holds.

Users around the world are successfully combining Java and C++, by means of JacORB and TAO implementations of the CORBA specifications. This shared experience amongst the communities, using TAO and JacORB as complimentary ORBs, has resulted in many interoperability issues being resolved. Many subtle behaviors have been harmonized as clients seek consistency between the two implementations. 

OCI used JacORB to implement its open source  OVATION tool.

OCI has helped many clients migrate succesfully from other Java CORBA implementations to JacORB. Clients have also used the activity to upgrade their use of CORBA, to take advantage of new capabilities. Click here  to find out about OCI Migration services.

JacORB is a CORBA ORB that runs well under Linux, and is more standards-compliant than some of the other big-name CORBA products.

JacORB is included in the J2EE open source product suite known as JBoss. OCI also provides support and a distribution for the version of Jboss derived from the jboss.org web site. 

For more information, visit the open source project web site at  www.jacorb.org

JacORB Features

JacORB is a CORBA V2.3 compliant, Java ORB (Object Request Broker) with the following features:

    • A fully multi threaded CORBA 2.3, IIOP 1.1 Compliant ORB
    • LGPL Software: Open Source, Zero Cost Licensing
    • 100% pure Java, JDK 1.3 and 1.4 compatible, also cooperates with Sun's JDK 1.2 classes (releases prior to 1.4 are compatible with JDK 1.1)
    • High performance IDL compiler, supports OMG IDL/Java language mapping rev. 2.3, OBV native IIOP, GIOP 1.2 and Bidirectional GIOP
    • POA (Portable Object Adapter) 
    • Client side AMI (Asynchronous Method Invocation) 
    • Quality of Service Policies (QoS)
    • ETF (Extensible Transport Framework) supporting pluggable protocols. 
    • Dynamic Invocation Interface (DII) and Dynamic Skeleton Interface (DSI)
    • Dynamic Management of Anys (DynAny)
    • Portable Interceptors (standard)  
    • Improved IIOP over SSL, includes KeyStoreManager
    • The following CORBA services
      • Interoperable naming service
      • Notification Service
      • Event Service
      • Transaction Service
      • Collection
      • Concurrency services
      • TradingService (supports trader links), an extension of Mark Spruiell's free JTrader
    • CORBA 2.3 Code set support
    • Support for HTTP tunneling
    • Both Interface Repository (IR) and Implementation Repository (IMR) 
    • IDL and Java source for all CORBA/COSS interfaces

Note: Through the magic of IDL most CORBA services can be shared amongst ORBs. (For instance only one naming service is required.) Therefore TAO C++ CORBA services can be invoked from Java CORBA implementations and vice versa. This enables shortcomings in one ORB's services, to be overcome by using another ORB's services. It also enables some consolidation of services, when developing a mixed language distributed system. If portability is an issue you may elect to use a Java based service. If performance and determinism is required, a C++ implementation with TAO may be more suitable.

Copyright © 2006 Object Computing, Inc. All rights reserved. | Privacy Policy