Skip to main content

Choosing Java Collection

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

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 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.

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.

Keys of the map are stored as java.lang.ref.WeakReference.
Entry will be removed automatically when the Key is not in use.

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.

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.

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.

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.


Popular posts from this blog

Masking Credit Card number in Java

Sometimes we need to mask crucial information like Credit Card Numbers, CVV numbers etc before storing  or logging the information. This example mask Credit Card Number (Except last 4 Digit) from a Text which contains information along with Credit Card Number.

The following example demonstrates how we can easily mask the credit card with Matcher and Pattern Classes. This Sample Code uses Matcher and Pattern.
Pattern Used in this sample is not optimized for Credit Card Numbers, this pattern will get any numerical numbers in the String Content.  Based on the Credit Card Type a more efficient and Strict RegEx can be used to mask the Credit Card.
/**Mask the Credit card number but last four digit value **/   Pattern PATTERN = Pattern.compile("[0-9]+"); String message = content; Matcher matcher = PATTERN.matcher(message); String maskingChar = "*"; StringBuilder finalMask = new StringBuilder(maskingChar); while …

Converting Java Map to String

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 out from Map C…

Invoking EJB deployed on a remote machine

Invoking EJB deployed on a remote machineIn 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();