How davidjavilabs/p3_corba works
Main Components
• Bibliotec.idl – The interface definition file that specifies the CORBA interfaces (the contract) for the library services.
• ServidorBiblioteca – The CORBA server implementation that registers its services with the naming service and implements the methods defined in the IDL.
• ClienteBiblioteca – The client application that acts as a consumer of the CORBA services offered by ServidorBiblioteca.
• ORB and Naming Service – The CORBA runtime used; “tnameserv” is used as the naming service to enable the client to locate the server.
Relationships and Interactions
• The IDL file acts as the central contract that ties the implementations (server) and consumers (clients) together.
• The ServidorBiblioteca registers its CORBA object with the naming service (provided by “tnameserv”) which acts as a directory.
• The ClienteBiblioteca uses the ORB to access the naming service, fetch the reference to the remote CORBA object, and then invokes library management methods.
• Data flows from the client to the naming service (for lookup), then to the server and back to the client.
Architectural Patterns and Design Principles
• There is a clear separation of concerns: the client is solely responsible for user interactions and method invocations, while the server encapsulates the business logic and state (such as tracking book popularity or rental history).
• The use of CORBA implies a distributed object architecture where the interface abstraction (IDL) decouples the client from the server implementation.
• The design leverages decoupling through middleware (ORB and naming service) which abstracts the network details.
Relevant Technologies
• Java (version 8) for implementation.
• CORBA for distributed object communication.
• The IDL compiler “idlj” is used for generating Java bindings from the IDL definitions.
• “tnameserv” as the CORBA naming service to aid in object lookup.