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 53
Setting and viewing ORB build properties
Make sure the IDL Compiler field is set to VisiBroker or VisiBroker (Borland
Enterprise Server AppServer Edition 6.0 and 5.2.1).
2 Set the Generated Code Options as needed:
■
In the Package field, enter the name of the package to generate code in. The
package name for definitions is prepended with the specified package name. If a
directory with the specified package name does not exist, it will be created. If the
package directory exists, its contents will be updated. Code is generated that
uses CORBA package resolution rules.
■
In the Include Path field, enter the location where other files that are referenced
from IDL files reside. Click the ellipsis (…) button beside this field to open a dialog
box that lets you browse the directory structure for the location of the files.
■
In the Additional Options field, enter any additional options for your IDL compiler,
as you would enter them when running the compiler from the command line.
■
The Symbols Defined For Conditional IDL Compilation list displays symbols that
have been defined for conditional IDL compilation. Click the New button to
display the Define New Symbol dialog box where you can define a new
conditional symbol. To remove a symbol from the list, select it then choose the
Delete button.
3 Choose the Paths node of the Project Properties dialog box. Make sure the
Required Libraries list includes the Borland Enterprise Server 6.0 Client.
4 Click OK to close the Project Properties dialog box.
5 Once you’ve created a Java interface file in your JBuilder project, right-click the file
in the project pane and choose Properties.
6 On the Build|VisiBroker node, select the Generate IDL and Generate IIOP options.
The dialog box should look like this:
■
Select the Java2IDL Generate IDL option to generate an Interface Definition
Language (IDL) file from a Java file or a class file. To support the distribution of
objects implemented in a variety of programming languages, an IDL file is used to
define the services offered by a particular distributed object.
■
Enter any Java2IDL command line options in the Options field. See the Borland
Enterprise Server VisiBroker documentation for command line options.
■
The Java2IIOP Generate IIOP Interface option generates an Internet InterORB
(Object Request Broker) Protocol (IIOP) compatible Java interface file from a
Java interface or class file. This is done by creating a new Java interface that
extends
org.omg.Corba.object. This Java interface can be used to describe
CORBA interfaces in place of using an Interface Definition Language (IDL) file to
describe the interfaces. The IIOP protocol maintains a basic set of functionality to
ensure inter-operability between client applications and server-based objects in a
Common Object Request Broker Architecture (CORBA).