Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
Chapter 6: Using JBuilder’s CORBA tools 45
Chapter
6
Chapter 6Using JBuilder’s CORBA tools
This chapter explains the CORBA (Common Object Request Broker Architecture) tools
available in JBuilder, including the VisiBroker ORB and IDL compilers.
The Common Object Request Broker Architecture (CORBA) allows distributed
applications to interoperate (application to application communication), regardless of
what language they are written in or where these applications reside.
The CORBA specification was adopted by the Object Management Group to address
the complexity and high cost of developing distributed object applications. CORBA
uses an object-oriented approach for creating software components that can be reused
and shared between applications. Each object encapsulates the details of its inner
workings and presents a well defined interface, which reduces application complexity.
The cost of developing applications is reduced, because once an object is
implemented and tested, it can be used over and over again.
The Object Request Broker (ORB) connects a client application with the objects it
wants to use. The client program does not need to know whether the object
implementation it is in communication with resides on the same computer or is located
on a remote computer somewhere on the network. The client program only needs to
know the object’s name and understand how to use the object’s interface. The ORB
takes care of the details of locating the object, routing the request, and returning the
result.
Note The ORB itself is not a separate process. It is a collection of libraries and network
resources that integrates within end-user applications, and allows your client
applications to locate and use objects.
JBuilder supports the VisiBroker ORB and the OrbixWeb ORB. JBuilder also provides
tools to configure other third-party ORBs.
How JBuilder and the VisiBroker ORB work together
The VisiBroker ORB provides a complete CORBA ORB runtime and supporting
development environment for building, deploying, and managing distributed Java
applications that are open, flexible, and inter-operable. The VisiBroker ORB is part of
the Borland Enterprise Server. Objects built with the VisiBroker ORB are easily
accessed by Web-based applications that communicate using OMG’s Internet Inter-
ORB Protocol (IIOP) standard for communication between distributed objects through