Browse Prior Art Database

Schema for Representing Java(tm) Objects in an LDAP Directory (RFC2713)

IP.com Disclosure Number: IPCOM000003308D
Original Publication Date: 1999-Oct-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 17 page(s) / 38K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

V. Ryan: AUTHOR [+3]

Abstract

This document defines the schema for representing Java(tm) objects in an LDAP directory [LDAPv3]. It defines schema elements to represent a Java serialized object [Serial], a Java marshalled object [RMI], a Java remote object [RMI], and a JNDI reference [JNDI].

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group V. Ryan

Request for Comments: 2713 S. Seligman

Category: Informational R. Lee

Sun Microsystems, Inc.

October 1999

Schema for Representing Java(tm) Objects in an LDAP Directory

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This document defines the schema for representing Java(tm) objects in

an LDAP directory [LDAPv3]. It defines schema elements to represent

a Java serialized object [Serial], a Java marshalled object [RMI], a

Java remote object [RMI], and a JNDI reference [JNDI].

1. Introduction

This document assumes that the reader has a general knowledge of the

Java programming language [Java]. For brevity we use the term "Java

object" in place of "object in the Java programming language"

throughout this text.

Traditionally, LDAP directories have been used to store data. Users

and programmers think of the directory as a hierarchy of directory

entries, each containing a set of attributes. You look up an entry

from the directory and extract the attribute(s) of interest. For

example, you can look up a person's telephone number from the

directory. Alternatively, you can search the directory for entries

with a particular set of attributes. For example, you can search for

all persons in the directory with the surname "Smith".

For applications written in the Java programming language, a kind of

data that is typically shared are Java objects themselves. For such

applications, it makes sense to be able to use the directory as a

repository for Java objects. The directory provides a centrally

administered, and possibly replicated, service for use by Java

applications distributed across the network.

For example, an application server might use the directory for

"registering" objects representing the services that it manages, so

that a client can later search the directory to locate those services

as it needs.

The motivation for this document is to define a common way for

applications to store and retrieve Java objects from the directory.

Using this common schema, any Java application that needs to read or

store Java objects in the directory can do so in an interoperable

way.

2 Representation of Java Objects

This document defines schema elements to represent three types of

Java objects: a Java serialized object, a Java marshalled object,

and a JNDI reference. A Java remote object is stored as either a Java

marshalled object or a JNDI reference.

2.1 Common Representations

A Java object is stored in the LDAP director...