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 Wed, 25 Apr 2007 13:04:11 GMT
That file format works if the name of the file is kerberos.ldif but does
not work if the name of the file is admin.ldif.

If this is specified (c:\\path\\to\\admin.ldif), the error message says
that c:\\path\\to\\?min.ldif can't be found.  Notice how the word
"admin" was changed by the code to "?min".  This seems to only happen
with the word "admin".

Mike Corum

-----Original Message-----
From: Enrique Rodriguez [] 
Sent: Tuesday, April 24, 2007 9:27 PM
Subject: Re: [ApacheDS] 1.5 Experience Not Good on Windows - Next
Problem - more on that

On 4/22/07, CORUM, M E [AG/1000] <> wrote:
> This code for automatically loading an ldif file using the
> property seems pretty badly broken on Windows for 1.5.  It always
> 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
> I can think of and it always defeats me.  Does anybody have this
> with 1.5 on Windows?

I believe that for Windows you would need the following format:


as in:

File f = new File("c:\\path\\to\\admin.ldif");

I've never tried it with just a directory path, so I'm surprised that
works.  Also, I'm not on Windows so please let us know if that File
format doesn't work.


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