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 57
Using the CORBA wizards
3 Click the OK button to set the options to be used by the VisiBroker idl2java
compiler, when the IDL file is compiled. Set the correct options so that when
compiled, Java interface definitions and Java client and server stubs and skeletons
are generated in a subdirectory of the project with the same name as the project.
When the Process This IDL File option is not checked, selecting OK saves the
selected options, but does not call the
idl2java compiler when the IDL file is
compiled. This means that the client stubs and server skeletons are not generated
when the IDL file is compiled.
Using the CORBA wizards
This section describes the JBuilder wizards that are available for CORBA
development. Wizards provide quick and easy development of IDL files and CORBA
client and server interfaces. These wizards are available only if your project is
configured for use with CORBA (Enterprise|Enterprise Setup|CORBA).
Sample IDL wizard
The Sample IDL wizard creates a simple IDL file that may be used to experiment with
the various CORBA tools that take an IDL file as input. The generated IDL file will
consist of a module and an interface containing a single method that can be
customized. This wizard is available on the Enterprise|CORBA page of the object
gallery (File|New).
The Sample IDL wizard looks like this:
CORBA Client Interface wizard
The CORBA Client Interface wizard produces a layer over idl2java-generated code
allowing a client application to easily invoke the interface methods of a running CORBA
server. You will be able to invoke methods in the interface that will be executed on a
CORBA server when you are connected to an Object Request Broker (ORB). This
wizard is only available if you have an IDL file in your project. It is available on the
Enterprise|CORBA page of the object gallery (File|New).