Q&A
| Q1: | What is the role of a resource adapter in the J2EE Connector architecture? |
| A1: | A resource adapter is a software driver that acts as a bridge between an EIS and a J2EE container. The J2EE Connector architecture specification defines the relationship between the EIS and an application server through the system contract. The system contract dictates the responsibilities of both parties with regard to connection pooling, transaction management, and security. These operations are transparent to application components, which simply invoke functions on the EIS via an API exposed by the resource adapter. |
| Q2: | I have a connection to an EIS, but I can't invoke its functions. What am I missing? |
| A2: | After you establish a connection to an EIS, you must create an Interaction object. All EIS functions are invoked through the Interaction object. |
| Q3: | Which Java technologies allow me to consume CORBA objects? |
| A3: | Two Java technologies allow you to consume CORBA objects—Java IDL and RMI over IIOP. To use Java IDL, you write a remote object's interface in IDL. RMI over IIOP uses the Java-specific RMI technology. Here you write a remote object's interface and then use the RMI compiler to generate stubs and skeletons for use with IIOP, a CORBA transport protocol. |
| Q4: | I have legacy code written in C that I would like to access remotely. How might I do this? |
| A4: | You can wrap C code using JNI. After you wrap the code, you can export it as an RMI object, which a client can access remotely. |
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.