Raw types when inheriting from HashMap, instead of <Object,Object> about json-simple HOT 14 OPEN

One feature of JSON.simple is to be compatible with JDK1.2 and later (both 
source
level and binary level, so it supports almost all of JDKs if not all), thus
JSON.simple doesn't use generic feature from JDK1.5 directly, but it does 
support all
of Map and List implementations with
JSONValue.toJSONString()/JSONValue.writeJSONString(). 

As a result, if an application/library can not use JSON.simple, it may be a 
build or
configuration issue of that application/library.

Thanks. 

I followed the link you provided, maybe you can type something like to make it 
work:

scala> o.put("a",new Integer(1))

Unfortunately no:

scala> obj.put("a",new Integer(1))
<console>:8: error: overloaded method value put with alternatives (K,V)V <and> 
((K
with K,_20)_20) forSome { type _20 >: V with V } cannot be applied to
(java.lang.String,java.lang.Integer)
       obj.put("a",new Integer(1))

The following should work:

scala> val o = new java.util.HashMap[String, Int]()
o: java.util.HashMap[String,Int] = {}

scala> o.put("a",1)
res5: Int = 0

scala> org.json.simple.JSONValue.toJSONString(o)
res6: java.lang.String = {"a":1}

Thanks a lot for the tip !

Is there any merit to releasing version 2.0 of this library to support language
improvements like generics and strongly typed collections?

Since JDK 1.4 is now reaching end of life, these types of updates would be 
really
useful for EE applications built on Java EE 5 where Javascript and Java are
responsible for data exchange.

Thank you Owen for your suggestion, I'll re-consider supporting of JDK2. The 
initial
intention is to make it compatible with ALL version of JDK as well as J2ME.

My two cents in favour of migrating to generics: compiling a java project 
(which uses json-simple) with javac's -Xlint option results into dozens of 
"[unchecked]" warnings. Thanks.

Until the library is updated to support generics this could be a case where 
@SuppressWarnings("unchecked") makes sense.

Another vote to leave ancient history behind and use generics.

Please, stop supporting old version of Java and start supporting generics!

One more vote for supporting generics; trying to iterate over the object in an 
idiomatic way like so:

   for (Map.Entry entry : jsonObject.entrySet()) { /* ... */ }

will lead to compile errors, because the compiler is seeing a Set of Objects 
instead of a set to Map.Entry instances.
Looking at 
http://zeroturnaround.com/rebellabs/java-tools-and-technologies-landscape-for-20
14/ slide 6: only 2% are still on Java 5, Java4 is not even mentioned anymore.

I have a best solution. Instead of this lib, use Gson.
Gson has generics and you need not try to catch an exception on every single 
interface method invocation.