I have 6 fields , where all belong to one single element . Similarly for the second element i need again 6 diff fields , so on......
i may need around 300 such elements.
When i retreive an element , i should be able to retreive all 6 fields pertaining to that.., Also i need not have unique fields from one element to other.
Which Collection class should i use...
Thanks in Advance
> I have 6 fields , where all belong to one single
> element . Similarly for the second element i need
> again 6 diff fields , so on......
>
> i may need around 300 such elements.
>
> When i retreive an element , i should be able to
> retreive all 6 fields pertaining to that.., Also
> i need not have unique fields from one element to
> other.
>
> Which Collection class should i use...
>
> Thanks in Advance
List! The list will contain user-defined objects which will hold the data for fields.
> List is an interface...dunno how you plan to use
> it....LinkedList is probably what you mean.
Yes, List is an interface and what I mean is to use anything which obeys that contract. I would use ArrayList, you use LinkedList and someone else might want to use a Vector. It's *still* a List. I might as well define my own class called List and use it, but it would still work the same way.
> Just consider defining a separate class which
> corresponds to your "elements" has has 6 fields.
>
> Fear-of-creating-classes is an anti-pattern and from
> your requirements it appears much more
> straightforward to define a new class than to abuse
> one of the collections classes.
I already mentioned that in my reply.
> > I have 6 fields , where all belong to one single
> > element . Similarly for the second element i need
> > again 6 diff fields , so on......
> >
> > i may need around 300 such elements.
> >
> > When i retreive an element , i should be able to
> > retreive all 6 fields pertaining to that..,
> Also
> i need not have unique fields from one element to
> other.
>
> Which Collection class should i use...
>
> Thanks in Advance
>
> List! The list will contain user-defined objects
> which will hold the data for fields.
Also depends on his retrieval criterion. If he wants to retrieve a specific object based on a unique identifier, I would think map would be the way to go with the Unique Identifier as they key.