Re: A HashMap isn't storing all of the entries.
Daniele Futtorovic wrote:
Stryder allegedly wrote:
I'm doing this...
HashMap<String, String[]> devObjectMap = new HashMap<String, S=
tring[]>(5);
Why do you declare it with an initial capacity of 5? That seems strikingly =
pointless.
Why do you declare the variable as 'HashMap' rather than 'Map'?
devObjectMap.put("DataExtension", new String[] {"ADLN_Customer",=
"ADLN_Story"});
devObjectMap.put("Email", new String[] {"ADLN","DRLN"});
devObjectMap.put("EmailSendDefinition", new String[] {"ADLN","AI=
LR"});
devObjectMap.put("ImportDefinition", new String[] {"ADLN_Custome=
r","ADLN_Story","AILR_Customer"});
devObjectMap.put("ContentArea", new String[] {"All_Subject_Lines=
","Date_issue"});
but it's dropping the first entry.
Wrong. It's not doing that. You are.
I'll bet 50=EF=BF=BD that it isn't actually dropping it, or that the reas=
on for
it lies in code residing outside of the java.* hierarchy.
I wouldn't take that bet, because you're almost certainly correct.
We won't know exactly where the problem is until the OP deigns to provide a=
http://sscce.org/
I got it to work by increasing the initial number of entries in the Hash=
Map constructor,
Wrong again. Also, why 5? What's wrong with 16?
By starting the map at 5 buckets and giving it 5 entries, you guaranteed at=
least one
growth cycle for the map. The load factor by default is 0.75, so you really=
should have at least
8 buckets for 5 entries.
You do realize that 'HashMap' increases size automatically, right, and it d=
oesn't drop
entries when it does so? Your data loss has nothing to do with the initial =
capacity of the
map.
so the question is pretty much academic unless I encounter it again.
But I'd be interested if anyone knows the answer.
PEBKAC.
Give us an SSCCE or give up on knowing what you did wrong.
By the way, 'devObjectMap' is a very unsatisfactory variable name.
--
Lew