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
![](/manual/borland-software/jbuilder-2005/server-user-manual/images/img-55.png)
56 Developing Applications for J2EE Servers
Setting and viewing IDL build properties
The tie mechanism offers an alternative when it is not convenient or possible to
have your implementation class inherit from the VisiBroker skeleton class. Object
implementation classes must inherit from the VisiBroker skeleton class. Java
does not allow multiple class inheritance and you may want your implementation
class to inherit from a different class.
Inheritance is easier to use than the tie mechanism because implementation
objects look and behave just like object references. If an implementation object
happens to be in the same process as a client using it, operation invocations
involve less overhead because no transport, indirection, or delegation of any kind
is required.
The tie mechanism provides a
delegator implementation class that inherits from
org.omg.CORBA.Object. The delegator implementation class does not provide any
semantics of its own. It simply delegates every call to the real implementation
class, which can be implemented separately and can inherit from whichever class
it wishes.
The
Operations class defines all of the methods that must be implemented by the
object implementation. This class acts as the delegate object for the associated
_tie class when the tie mechanism is used.
■
Click the ellipsis (…) button next to the Include Path field to display the Select
Directory dialog box, where you can select a directory to search for the list of files
to include in the build. You must select a directory that contains an
.idl file.
■
Enter options not available in this dialog box in the Additional Options field.
■
The IDL2package Setting options are the equivalent of the command line
parameter
-idl2package idl pkg. If any part of the IDL file is in the scope
::CORBA,the generated is code is placed in the org.omg.CORBA package. When this
option is not set, the generated code uses the CORBA package resolution rules.
■
IDL Definition — The definition in scope of IDL.
■
Package — The Java package into which to place the IDL definition.
2 Click the Conditional Defines tab to set symbols defined for conditional compilation.
■
The Symbols Defined for Conditional IDL Compilation list displays a list of
symbols defined for conditional IDL compilation.
■
Click the New button to display the Define New Symbol dialog box, where you to
define a symbol name for conditional IDL compilation, for example
#define name
def
.
■
Choose a symbol and click the Delete button to delete the selected symbol from
the list of symbols defined for conditional compilation.