Skip to main content

New in Dolphin - Java 7


With Dolphin java introduced cool new features like:

1. Strings in “switch” block

     switch(s) {
          case “Apple”:
          // do something;

          case “Orange”:
          // do something;


          default :
     }



     2. <> (Diamond) operator – Type inference for generic instance creation
E.g List > list = new ArrayList>();
vis-à-vis
List > list = new ArrayList <> ();
Empty diamond braces is required and it's not a typo :).



     3. Single Catch for multiple Exceptions with "|" operator
          try {
          // Reflective operations calling Class.forName,
          // Class.newInstance, Class.getMethod, Method.invoke, etc.
     } catch (final ClassNotFoundException |      InstantiationException | NoSuchMethodException |      InvocationTargetException e) {
          log(e)
          throw e;
     }


     4. Also in Java 7, this will work
     public void rethrowException(String exceptionName) throws FirstException, SecondException {
          try { // ...
          } catch (Exception e) {
          throw e;
     }
}



     5. Try-with-resources statement – basic objective is to facilitate automatic resource management, simplify coding and highlight pertinent exceptions e.g.
     try (InputStream in = new FileInputStream(src);
     OutputStream out = new FileOutputStream(dest);) {
          byte buf = new byte[8192];
          int n;
          while ((n = in.read(buf)) >= 0)
               out.write(buf, 0, n);
          }

Comments

  1. Oh these are nice - certainly will take care of much of the boiler plate code that one has to write for many of these exceedingly common situations! Thanks - was useful.

    ReplyDelete
  2. Thanks Sachin, I agree try block looks much better now...

    ReplyDelete
  3. Nice to see this blog Subodh, My name is also Subodh Gupta :D

    ReplyDelete

Post a Comment

Popular posts from this blog

Interview at Progress Software

I have given a lot of interviews before however, this one was special. Let me start from the beginning. I got a call from Progress Software and was scheduled for the first telephonic discussion. Next day, I got a call from HR and she asked me questions on Java and a few basic puzzles.  After clearing the previous round, I got scheduled for the second telephonic interview. This interview covered Java, design-related problems and algorithms. After a week, I got a call from the HR for the onsite interviews in Hyderabad. This is the first time I googled about Progress Software. I said yes for the onsite interviews. Journey to onsite started not as planned after my flight got delayed. Because of fog-related delay in Delhi, I reached the PSI (Progress Software India) office couple of hours late.  HR introduced me to the first interviewer. The interviewer explained the first round. It was a coding round (I am not a big fan of coding rounds), the problem was ...

java.net.SocketException: Connection reset

I am able to fix the problem via setting the following params on the HTTPClient class... client.getParams().setParameter("http.socket.timeout", new Integer(0)); client.getParams().setParameter("http.connection.stalecheck", new Boolean(true)); java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77) at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:105) at org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1115) at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1832) at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1590) at org.apache.commons.httpclient.HttpMethodBase.execute(...

CXF-RS: Java Code Generation from xml/xsd

Cleaner approach is to use xjc like this: Continue to dirty approach below if u need to: When working with CXF-RS services often we start with XML message that will be served. After that we go through endless iteration of generating the right Java POJO's for the XML. The library like apache XMLBeans generate the Java code but the code generated is not what a developer would write and generally tedious to modify and understand. I have come across a work around for generating Java classes from XSD (xml) which is very close to what a developer with decent experience will write.  Follow the steps given below to explore the solution: 1. Generate the wsdl from from xsd as given in at this link  ( http://cxf.apache.org/docs/xsd-to-wsdl.html ). 2. The Java classes can be generated from wsdl from maven plugin entry below find complete details here   http://cxf.apache.org/docs/maven-cxf-codegen-plugin-wsdl-to-java.html org.apache.cxf cxf-codegen-plugin ...