Constructors with too many parameters

Regarding the Array, the same arguments apply as to the Map. It's neater, but you have to do extra checking to make sure that everything is there, and you need to know which index will contain which String.

Params could be either Long Integer Double Or String

>>I would prefer the 10 Strings in this case, for the simple reason that it is very clear that you need 10 strings.

I wouldn't go for this for below reasons,

1. It doesn't look good
2. Occupies more space in the Stack
3. Difficult to maintain...

>>Params could be either Long Integer Double Or String

the best option is to go with getter & setter with empty constructor or few constructrs with few required params

>>Params could be either Long Integer Double Or String

U can use "instance of" operator with each object in the constructor... and put into map..

Elements in Map will be "key, value pair", So These strings are.. keys or values.. or..?

>>U can use "instance of" operator with each object in the constructor... and put into map..

this is an overhead, would be avoided if you use getter & setter!

Thanks for the answers.
Array cannot be used due to instance of overhead.
Some in constructor and some as setters cannot be used as all are mandatory.  

So considering the objects can be Integer, Long , Double or String what is the best design practice?

>> Array cannot be used due to instance of overhead.

If you go ahead, with getters and setters then you are having function overhead...

If you have 10 parameters in the constructor, then you are having neatness/readability overhead..

Overhead is always there, when more parameters are involved..

Going ahead with array paramter (or some other collection object) is neat..

and even the parameters are increased, the interface for creating the objects will not be changed.

And this option provides you with the extensibility..

>>If you go ahead, with getters and setters then you are having function overhead...

but this is how the Java beans are designed and working! Array can not hold diff datatypes!

>>Some in constructor and some as setters cannot be used as all are mandatory.

still I would suggest getters & setters though you can not make compile time safty, if the user not supplying the required parameters, it sould be a programatical error i.e., runtime exception as ArrayIndexOutofBounds exception with array! having as params in constructor is not best approach if the number of params are more!

@inditrozen

>> which will insert params into Map

For best solution, Can u please tell, how 10 parameters are inserted into MAP..

I mean insert 5 key value pairs.. or

all 10 params as key's with some other value objects or

all 10 params as value's with some other key's ..

>>@inditrozen

>>which will insert params into Map

>>For best solution, Can u please tell, how 10 parameters are inserted into MAP..

all 10 parameters are to be inserted into the map as different entry, 10 Constants for keys are already defined inside the class.

>>all 10 parameters are to be inserted into the map as different entry, 10 Constants for keys are already defined inside the class.

in this case better take the map as the parameter in the constructor and validate the map if it is filled with all, if not through a runtime exception saying the missed in values!

I already said.. in My comment with ID:20732774

>> Going ahead with array paramter (or some other collection object) is neat..

>> Going ahead with array paramter (or some other collection object) is neat..

I have made that statement in my first comment :)

>>you can define the constructor with Map then than having 10 prams!

Great..!

but it says constructor with map and getter & setters..  :-)

Its OK

>>but it says constructor with map and getter & setters..  :-)

thats another option I have given!

Cool ... !

Accepted array?

if the arguments are different types, how can you pass them in a Array?