| Home | Previous Lesson: IDL Next Lesson: Static and dynamic invocation |
In CORBA, methods invocation can be either static or dynamic. For static invocation, the client application needs to have prior knowledge of the object services that it will need, so the IDL specification must be incorporated into the client as well as the server object, using your chosen programming language. You take care of this by using an IDL compiler (supplied by your ORB vendor) to compile the IDL into client-side stub routines and server-side skeleton code. Stub is something like the proxy object you created in the earlier topics. For example, if you are using Java for the client and C++ for the object, you would use an IDL-to-Java compiler to make the stubs in Java and an IDL-to-C++ compiler to make the skeleton code in C++. You can then write your client using calls to the stub routines to invoke the server object�s methods. You do not need to do any coding for the stubs. You use the skeleton code, along with the code that you write, to implement the server object.
Once you have completed your coding for the client and object, you can use your language compiler to compile and link them. The stub and skeleton code combine with the ORB to implement location transparency.
| Home | Previous Lesson: IDL Next Lesson: Static and dynamic invocation |