Abstract
Almost every application requires some means of keeping data across program runs. Most applications use a file or database for the storage or persistence of data. However, databases are not typically used to store objects, particularly Java objects. On the other hand, flat files alone do not cope well with object structure. What is required is some means to preserve the state of a Java object so that it may be easily stored and subsequently restored to its original state.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
This is addressed in JavaEE (Java Enterprise Edition) within the scope of Enterprise Java-Beans (EJB) architecture.
The skeleton class is not generated from JDK 1.2 onwards.
Use $ rmic –v1.2 rmi1.Server1Impl for JDK 1.2 onwards. This suppresses the generation of the skeleton class.
The Sun Java Enterprise System implements RMI-IIOP (a cross between RMI and IIOP) to enable objects from different operating platforms to communicate with one another.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2008 Springer-Verlag London Limited
About this chapter
Cite this chapter
Poo, D., Kiong, D., Ashok, S. (2008). Object Serialization and Remote Method Invocation. In: Object-Oriented Programming and Java. Springer, London. https://doi.org/10.1007/978-1-84628-963-7_16
Download citation
DOI: https://doi.org/10.1007/978-1-84628-963-7_16
Publisher Name: Springer, London
Print ISBN: 978-1-84628-962-0
Online ISBN: 978-1-84628-963-7
eBook Packages: Computer ScienceComputer Science (R0)