Hey Alex,
SNIP
My point to you was to just browse the ou=schema partition which
basically displays the schema elements using a meta schema that
describes schema entities.
Coollll (It's my word of the day :-) )
It's very easy while browsing this area to
understand the structure of the tree there and infer the schema used.
By
doing this you can use LDAP to more efficiently query the schema
information when you cannot do the same under the schemaSubentry which
is the mechanism supported by the LDAP standard.
Aha! Even more cooolll.
Hope your cold gets better soon. I always chomp on a clove of Raw
Garlic (It releases a very powerful antibiotic when crushed - has to be
raw though). It's also great if people are inviting you to too many
meetings at work :-)
Oh thanks Ole but I am a vampire so that might not be so good for me.
Yeeaaah - I thought you looked a little pale in the fishing
pictures...especially for someone living in Florida :-)
Thanks,
- Ole
:)
Regards,
Alex
Thanks,
- Ole
Alex Karasulu wrote:
> Stefan is absolutely correct here. Take a minute and start ADS 1.5.0
> and use LDAP Studio to browse the schema partition (ou=schema). By
> browsing this partition you'll see the proper patterns required.
>
> Alex
>
> On 4/9/07, *Stefan Seelmann* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote:
>
> Hi Ole,
>
> > When adding a new ObjectClass to the Schema
> > named "org.apache.tuscany.User"
>
> An objectClass or attributeType name must be an OID (object
identifier),
> that is defined as follows in RFC4512:
> oid = descr / numericoid
> descr = keystring
> keystring = leadkeychar *keychar
> leadkeychar = ALPHA
> keychar = ALPHA / DIGIT / HYPHEN
> numericoid = number 1*( DOT number )
> ... and so on
>
> So your name could be either something like
> 0.11.222.3333.44444
> or
> org-apache-tuscany-User
>
>
> > is this how I do the DN?:
> >
> > DN: objectClass=org.apache.tuscany.User, ou=objectClasses,
ou=Schema
> >
>
> The DNs of the other objectclases in the schema looks like this:
> "m-oid= 2.5.6.5 <http://2.5.6.5>
<http://2.5.6.5>,ou=objectClasses,cn=core,ou=schema"
>
> So I would recommend to create your own schema suffix under
ou=schema
> where you could put the DAS schema. Here is an example in
LDIF format,
> how this could look like:
>
> ----------------------------------------------
> dn: cn=ecore,ou=schema
> objectClass: metaSchema
> objectClass: top
> cn: ecore
> m-dependencies: core
> m-dependencies: system
>
> dn: ou=objectClasses,cn=ecore,ou=schema
> objectClass: organizationalUnit
> objectClass: top
> ou: objectClasses
>
> dn: m-oid=0.11.222.3333.44444
,ou=objectClasses,cn=ecore,ou=schema
> objectClass: metaObjectclass
> objectClass: metaTop
> objectClass: top
> m-oid: 0.11.222.3333.44444
> m-description: org.apache.tuscany.User
> m-must: cn
> m-name: org-apache-tuscany-User
> m-obsolete: FALSE
> m-supObjectClass: top
> m-typeObjectClass: AUXILIARY
> ----------------------------------------------
>
>
> BTW, the new schema feature is really cool. Once you have
created the
> "ou=objectClasses,cn=ecore,ou=schema" entry you could add new
schema
> elements by adding simple string values to cn=schema:
>
> -------------------------------------------
> dn: cn=schema
> changetype: modify
> add: objectClasses
> objectClasses: ( 0.11.222.3333.44444 NAME
'org-apache-tuscany-User'
> DESC 'org.apache.tuscany.User' SUP top AUXILIARY MUST cn
> X-SCHEMA 'ecore' )
> -
> -------------------------------------------
>
>
> Regards,
> Stefan
>
>
