Lines Matching refs:Java
14 Schema for Representing Java(tm) Objects in an LDAP Directory
28 This document defines the schema for representing Java(tm) objects in
30 a Java serialized object [Serial], a Java marshalled object [RMI], a
31 Java remote object [RMI], and a JNDI reference [JNDI].
36 Java programming language [Java]. For brevity we use the term "Java
37 object" in place of "object in the Java programming language"
49 For applications written in the Java programming language, a kind of
50 data that is typically shared are Java objects themselves. For such
52 repository for Java objects. The directory provides a centrally
53 administered, and possibly replicated, service for use by Java
60 RFC 2713 Schema for Java Objects October 1999
69 applications to store and retrieve Java objects from the directory.
70 Using this common schema, any Java application that needs to read or
71 store Java objects in the directory can do so in an interoperable
74 2 Representation of Java Objects
77 Java objects: a Java serialized object, a Java marshalled object,
78 and a JNDI reference. A Java remote object is stored as either a Java
83 A Java object is stored in the LDAP directory by using the object
84 class javaObject. This is the base class from which other Java object
92 to storing a Java object. It is a structural object class. In cases
102 used to store the fully qualified name of the object's Java class
116 RFC 2713 Schema for Java Objects October 1999
120 fully qualified names of the object's Java classes and interfaces
134 Java objects might use javaClassName to produce a summary of the
135 names and types of Java objects in that directory. Another
141 store a pointer (URL) to the Java documentation for the class.
142 description is used to store a textual description of a Java object
150 a copy of the object. A Java object is "serializable" if its class
161 The Java platform specifies a default algorithm by which serializable
162 objects are serialized. A Java class can also override this default
172 RFC 2713 Schema for Java Objects October 1999
180 definitions. For example, the Java application might include in its
228 RFC 2713 Schema for Java Objects October 1999
249 MarshalledObject is available only on the Java 2 Platform, Standard
284 RFC 2713 Schema for Java Objects October 1999
289 Java Naming and Directory Interface(tm) (JNDI) is a directory access
290 API specified in the Java programming language [JNDI]. It provides
291 an object-oriented view of the directory, allowing Java objects to be
303 A JNDI reference is a Java object of class javax.naming.Reference.
305 and an ordered list of addresses. An address is a Java object of
319 the Java class name of that object, and the class name and location
340 RFC 2713 Schema for Java Objects October 1999
355 The Java Remote Method Invocation (RMI) system [RMI] is a mechanism
356 that enables an object on one Java virtual machine to invoke methods
357 on an object in another Java virtual machine. Any object whose
396 RFC 2713 Schema for Java Objects October 1999
399 RMI can be supported using different protocols: the Java Remote
403 RMI over IIOP allows Java remote objects to communicate with CORBA
404 objects which might be written in a non-Java programming language
438 MarshalledObject is available only on the Java 2 Platform, Standard
440 as a MarshalledObject can only be read by clients using the the Java
452 RFC 2713 Schema for Java Objects October 1999
477 of the Java objects.
493 the RMI infrastructure available on the Java platform to automate how
508 RFC 2713 Schema for Java Objects October 1999
540 This attribute stores the fully qualified name of the Java object's
547 DESC 'Fully qualified name of distinguished Java class or
564 RFC 2713 Schema for Java Objects October 1999
569 This attribute stores the Java class definition's locations. It
575 codebase for loading in the Java class definition.
580 viewed as an alternate source for loading the Java class definition.
581 See [Java] for information regarding class loading.
594 This attribute stores the Java object's fully qualified class or
605 DESC 'Fully qualified Java class or interface name'
620 RFC 2713 Schema for Java Objects October 1999
625 This attribute stores the serialized form of a Java object. The
632 DESC 'Serialized form of a Java object'
649 DESC 'Fully qualified Java class name of a JNDI object factory'
658 reference. Each of its values represents one address, a Java object
676 RFC 2713 Schema for Java Objects October 1999
690 type, and then by another delimiter. If the address is of Java class
713 This attribute stores a pointer to the Java documentation for the
722 DESC 'The Java documentation for the class'
732 RFC 2713 Schema for Java Objects October 1999
747 This structural object class represents a container for a Java
752 DESC 'Container for a Java object'
760 This abstract object class represents a Java object. A javaObject
766 DESC 'Java object representation'
788 RFC 2713 Schema for Java Objects October 1999
793 This auxiliary object class represents a Java serialized object. It
798 DESC 'Java serialized object'
806 This auxiliary object class represents a Java marshalled object. It
811 DESC 'Java marshalled object'
844 RFC 2713 Schema for Java Objects October 1999
876 [Java] Ken Arnold and James Gosling, "The Java(tm) Programming
879 [JNDI] Java Software, Sun Microsystems, Inc., "The Java(tm)
887 [RMI] Java Software, Sun Microsystems, Inc., "Remote Method
900 RFC 2713 Schema for Java Objects October 1999
903 [RMI-IIOP] IBM and Java Software, Sun Microsystems, Inc., "RMI over
907 [Serial] Java Software, Sun Microsystems, Inc., "Object
956 RFC 2713 Schema for Java Objects October 1999
965 DESC 'Fully qualified name of distinguished Java class or interface'
980 DESC 'Serialized form of a Java object'
987 DESC 'Fully qualified Java class name of a JNDI object factory'
1002 DESC 'The Java documentation for the class'
1012 RFC 2713 Schema for Java Objects October 1999
1017 DESC 'Fully qualified Java class or interface name'
1035 DESC 'Container for a Java object'
1043 DESC 'Java object representation'
1052 DESC 'Java serialized object'
1068 RFC 2713 Schema for Java Objects October 1999
1081 DESC 'Java marshalled object'
1124 RFC 2713 Schema for Java Objects October 1999