Choosing Java Collection

By -
The following section summarizes the various Collection Classes as of Java 7 and their important attributes Including HashMap which is not in Collection Framework.

HashMap.
It provides constant time operation for operations like get and put and remove.
Iteration over the Collection values requires time proportional to the capacity of the Map.(values()).
Default load factor is .75.
HashMap does not maintain the order.
HashMap is not synchronized.

LinkedHashMap
LinkedHashMap orders are maintained
It provdes constant-time performance for operations like get, put and remove.
Performace is slightly slower then HashMap due to the overhead of maintaining Linked List.
Re-insertion does not effect the insertion order.
Iteration over the collection values is proportional to the size of the map  regardless capacity.
TreeMap
Red-Black tree based implementation.
Implement the SortedMap Interface.
Map is ascending Key order of the natural order.
It has log(n) time cost for  contansKey, put, get and remove operations.
operations lke get and put are slower then HashMap.

WeakHashMap
Keys of the map are stored as java.lang.ref.WeakReference.
Entry will be removed automatically when the Key is not in use.
Set
Set does not contain duplicate items.
It contains maximum one null item.
add method put the new item to the set if it does not present already and return true/false.

 HashSet
It does not allow duplicate.
It does not guarantee the iteration order of the elements.
It provides constant time performance for operations like add,remove,contains, size.

 LinkedHashSet
It maintains the insertion order.
Insertion order is not effected by reinsertion.
It provides constant time operations like  add, contains,remove.
Iteration over the collection values is proportional to the size of the map regardless capacity.
TreeSet
Set is sorted on ascending order of the elements.
It has log(n) time cost for  contansKey, put, get and remove operations.
It implements the SortedSet Interface.

Comments

Post a Comment

Popular posts from this blog

Converting Java Map to String

By -
Java Collections framework, String manipulation etc is something that we often encounter in Development process. For processing collections (like checking null/empty, Intersection, Disjunction) We do have some of the very use full libraries. Some of the Collection related libraries are Apche Commons Collections and Google  Collections(Guava). Problem Use Case This article explains how to convert a Java Map to String(and vice versa) using different libraries and technique. One way is to use StringBuilder(Or String) and loop though the Map and build the String by applying some sort of separator ( for key:value and entry). Here we have to take care of the null value etc. Without Any Library If we want to convert the map to a String with key value separator and also individual entry seperator in the resulting String, we have to write code for that. For a simple Map, we have to iterate though the map, take care of the null values etc. Following is a sample to get String built
Read more

Difference between volatile and synchronized

By -
volatile is a field modifier, while synchronized modifies code blocks and methods. So we can specify three variations of a simple accessor using those two keywords: int i1; int geti1() {return i1;} volatile int i2; int geti2() {return i2;} int i3; synchronized int geti3() {return i3;} geti1() accesses the value currently stored in i1 in the current thread . Threads can have local copies of variables, and the data does not have to be the same as the data held in other threads. In particular, another thread may have updated i1 in it's thread, but the value in the current thread could be different from that updated value. In fact Java has the idea of a "main" memory, and this is the memory that holds the current "correct" value for variables. Threads can have their own copy of data for variables, and the thread copy can be different from the "main" memory. So in fact, it is possible for the "main"
Read more

Invoking EJB deployed on a remote machine

By -
Invoking EJB deployed on a remote machine In case we are calling remote ejb( ejb deployed on remote machines), The JNDI lookup might lookup like, Properties env = new Properties(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); env.put(Context.PROVIDER_URL, "XX.XXX.XX.XX:1099"); env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); Context ctx = new InitialContext(env); If we are calling local ejb then we can simply create InitialContext without any parameters. Like, Context ctx = new InitialContext();
Read more