![]() |
![]() |
e-docs > Tuxedo > Using CORBA Server-to-Server Communication > Java Joint Client/Server Applications |
Using CORBA Server-to-Server Communication
|
Java Joint Client/Server Applications
This topic includes the following sections:
Development Process
Table 3-1 outlines the development process for Java joint client/server applications.
Table 3-1 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 (filename.xml) for it. However, you still need to create a Server Description File for the BEA Tuxedo objects in your BEA Tuxedo application.
Support for Joint Client/Server Applications
BEA Tuxedo CORBA supports Java clients and joint client /servers.
Note: 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.
Figure 3-1 The Concept of a Joint Client/Server Application
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. The Java Advanced sample application is implemented using the BEA Simple Events API.
![]() |
![]() |
![]() |
![]() |
||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |