This topic includes the following sections:
|Notes:||The BEA Tuxedo CORBA Java client and BEA Tuxedo CORBA Java client ORB were deprecated in Tuxedo 8.1 and are no longer supported. All BEA Tuxedo CORBA Java client and BEA Tuxedo CORBA Java client ORB text references, associated code samples, should only be used to help implement/run third party Java ORB libraries, and for programmer reference only.|
|Note:||Technical support for third party CORBA Java ORBs should be provided by their respective vendors. BEA Tuxedo does not provide any technical support or documentation for third party CORBA Java ORBs.|
Table 3-1 outlines the development process for Java joint client/server applications.
Because the callback object in a joint client/server application is not transactional and has no object management capabilities, you do not need to create a Server Description File (
.xml) for it. However, you still need to create a Server Description File for the BEA Tuxedo objects in your BEA Tuxedo application.
|Notes:||Release 8.0 of the CORBA environment of the BEA Tuxedo product does not support Java servers. Support for Java servers was included in versions 5.0 and 5.1 of the BEA WebLogic Enterprise product. That support was removed when BEA WebLogic Enterprise was merged with BEA Tuxedo in release 8.0.|
An implementation of a joint client/server employs a callback object. Figure 3-1 illustrates the concept of a joint client/server application using a callback object.
For a complete example of a joint client/server application, see Chapter 6, "Building the Advanced Sample Application," in Using the CORBA Notification Service. The subscriber component in the Advanced sample application implements a joint client/server application.