Thanks Alex,
LDAP Studio is so nice, I'm almost scared to look.
Incidentally, do you know (Stefan?) if LDAP Studio
has a Schema drill down "Outline View" like the one
in JXPlorer? I think in JXPlorer (Just from looking
at the "Writing Java Objects to ApacheDS Part1" article),
has a Schema tab, and below it one can drill down into
the various Schema nodes. I looked LDAP Studio Schema Browser,
and noticed the tabs with Schema node categories, and I was thinking
that it would probably trigger a drill down view in the outline pane...
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 :-)
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]>> 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>,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
