directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "CORUM, M E [AG/1000]" <>
Subject RE: [ApacheDS] 1.5 Experience Not Good on Windows - Next Problem - more on that
Date Mon, 23 Apr 2007 03:43:47 GMT
This code for automatically loading an ldif file using the ldifDirectory
property seems pretty badly broken on Windows for 1.5.  It always strips
off the first two characters of the file name and puts a question mark
in front it.  I've tried every combination of file names and directories
I can think of and it always defeats me.  Does anybody have this working
with 1.5 on Windows?


-----Original Message-----
From: CORUM, M E [AG/1000] 
Sent: Sunday, April 22, 2007 10:33 PM
To: ''
Subject: RE: [ApacheDS] 1.5 Experience Not Good on Windows - Next

Now, I'm trying to use the following code in the server.xml:

    <property name="ldifDirectory">
    <property name="ldifFilters">

I've tried every value I can think of to try for the "ldifDirectory"
value.  I tried a file name at the end and that ended up with the same
exact error as if I didn't use a file name.  The error from the code
above is listed below.  I have one file in that directory called
"admin.ldif".  Can anybody suggest syntax that might work?  I tried all
the suggestions in the comments in the file and none worked (although I
didn't try the file:/// syntax - is that really the only one that
works?).  Whether I specify a file name or not, it find the file and
swallows the first two letters and puts in a question mark, hmmm.

[22:28:44] ERROR [] - Failed on, String[])
javax.naming.NamingException: Invalid value :


This e-mail message may contain privileged and/or confidential information, and is intended
to be received only by persons entitled to receive such information. If you have received
this e-mail in error, please notify the sender immediately. Please delete it and all attachments
from any servers, hard drives or any other media. Other use of this e-mail by you is strictly

All e-mails and attachments sent and received are subject to monitoring, reading and archival
by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence
of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any
such code transmitted by or accompanying this e-mail or any attachment.

View raw message