and another thing... the attributes come as..
<attr name="o">
<value>abc</value>
</attr>
in dsml, the values are assumed to be base64 encoded unless the encoding is
explicitly mentioned as an attribute in the value tag. now the dsml file
produced by castor does not include any encoding attribute. so when we'll
read it, a value which is actually not encoded will be interpreted as an
encoded one..
how do we resolve these issues?
-----Original Message-----
From: Jaspreet Singh [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 23, 2001 4:38 PM
To: [EMAIL PROTECTED]
Subject: [castor-dev] a question regarding ldap to dsml functionality...
help.
Hi all !
I am facing a problem that when i convert ldap database to a dsml
file using castor, the dn's in the dsml file are relative i.e for the
topmost dn i'll have dn="" for others it will be dn="ou=abc" and so on. But
the problem is that when i try to upload this data to the ldap repository,
it throws an exception as -
javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - root
DSE exists]; remaining name ''
Now the conversion from ldap to dsml is of no use to me if i am not able to
setup my ldap repository using this this data.
Is there any way to force castor to use full dn's instead of rdn's ??
thanks in advance
Jaspreet
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
