Patterns in Java, volume 1: a catalog of reusable design patterns illustrated with UML
Patterns in Java, volume 1: a catalog of reusable design patterns illustrated with UML
Object serialization for marshalling data in a Java interface to MPI
JAVA '99 Proceedings of the ACM 1999 conference on Java Grande
Mostly-copying reachability-based orthogonal persistence
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Java virtual machine support for object serialization
Proceedings of the 2001 joint ACM-ISCOPE conference on Java Grande
Advanced Java 2 Platform How to Program
Advanced Java 2 Platform How to Program
IEEE Internet Computing
Efficient RMI: Dynamic Specialization of Object Serialization
ICDCS '00 Proceedings of the The 20th International Conference on Distributed Computing Systems ( ICDCS 2000)
ICCL '98 Proceedings of the 1998 International Conference on Computer Languages
Specializing The Java Object Serialization Using Partial Evaluation For A Faster RMI
ICPADS '01 Proceedings of the Eighth International Conference on Parallel and Distributed Systems
Object serialization analysis and comparison in Java and .NET
ACM SIGPLAN Notices
Differential Serialization for Optimized SOAP Performance
HPDC '04 Proceedings of the 13th IEEE International Symposium on High Performance Distributed Computing
Hi-index | 0.02 |
Long Term Persistence for JavaBeans (LTP) is an API that supports a general mechanism for serializing JavaBeans into an XML-based text format and vice versa. As Java programming language does not currently support orthogonal persistence, a programmer can choose to convert the internal state of an application into a permanent storage and vice versa using the LTP API. In this paper, we propose a mechanism that is extensible and optional for LTP, without modifying the LTP specification, to maximize the flexibility and extendibility of Java applications. Our approach embeds scripts in an encoded XML text in order to reconstruct missing objects, or to create some additional helper objects during the subsequent decoding process. Moreover, as the decoding process may take too much time to instantiate certain heavyweight objects, the proposed mechanism also supports an optional cache pool to speed it up.