Re: Comments on draft-ryan-java-schema-02

[Manish Gupta <manishg@cisco.com>]

That is what I expected, however, teh javaObject schema is currently
defined as

( 1.3.6.1.4.1.42.2.27.4.2.4
         NAME 'javaObject'
         DESC 'Java object representation'
         SUP top
         ABSTRACT
         MUST ( javaClassName )
         MAY ( javaClassNames $
               javaCodebase $
               javaDoc $
               description )
       )

thus I assumed that javaClassName *had* to be the naming attribute. Is
there a typo/omission in the javaObject definition in the i-d?

Manish
At 05:11 PM 5/19/99 +0100, Vincent Ryan wrote:
>Manish Gupta wrote:
>> 
>> I did not intend to store multiple serialzied Java objects in one LDAP
entry.
>> 
>> Perhaps an example will help clarify my question/comment. Let us say that I
>> have 2 different Java objects, o1 and o2, corresponding to the same Java
>> class, Foo. Now if I wanted to store the serialized form of both of these
>> Java objects in an LDAP directory, I would have to store them in different
>> portions(containers) of the directory as the RDN of each of them would be
>> Foo (its javaClassName).
>
>Actually that's not necessary. The javaClassName attribute isn't used
>for naming the entry. The javaSerializedObject object class inherits
>the cn attribute from the javaObject object class. It's better to use
>cn to name the entry. For example,
>
>    cn=o1, ou=Java Objects, o=cisco.com
>    cn=o2, ou=Java Objects, o=cisco.com
>