java-7

Is it possible to ignore the exception thrown when a resource is closed using a try-with-resources statement? Example: class MyResource implements AutoCloseable{ @Override public void close() throws Exception { throw new Exception("Could not close"); } public void read() throws Exception{ } } //this method prints an exception "Could not close" //I want to ignore it public static void test(){ try(MyResource r = new MyResource()){ r.read(); } catch (Exception e) { System.out.println("Exception: " + e.getMessage()); } } Or should I continue to close in a finally instead? public static void test2(

I'm aware that the runtime features of Java 7 are not available with Java 6 but since no new byte code has been added the new byte code invokedynamic is only relevant for non-Java languages, I was wondering how hard it would be to convert Java 7 source code (new switch statement, diamond operator) to pure Java 6 (i.e. to be able to start to convert the source to Java 7 without losing Java 6 compatibility). Any pointers? karmakaze Mark a .class file output by Java 7 javac with version 1.6.0 (i.e. 0x32) printf "\x00\x00\x00\x32" |dd of=Example.class seek=4 bs=1 count=4 conv=notrunc (according to

When I compile my project in eclipse indigo using JDK 7, I get the following error dialog with the following stacktrace Exception in thread "main" java.lang.VerifyError: Expecting a stackmap frame at branch target 32 in method ... at offset 0 at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.lang.Class.getMethod0(Unknown Source) at java.lang.Class.getMethod(Unknown Source) at sun.launcher.LauncherHelper.getMainMethod(Unknown Source) at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source) I've found a relevant bug

I have used com.sun.image.codec.jpeg.JPEGImageEncoder to handle JPEG images, like charts and others, in my webapp. Now, I am updating my machine to use JDK7, but this version deprecated this class. Below is the code that I need to change: public void processChart(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { response.setContentType("image/jpeg"); out = response.getOutputStream(); response.setHeader("Pragma", "no-cache"); response.setHeader("Cache-Control", "no-cache"); response.setDateHeader("Expires",0); try { int w = Integer.parseInt(request

This question already has an answer here: Closure in Java 7 [closed] 7 answers I have heard that closures could be introduced in the next Java standard that is scheduled to be released somewhere around next summer. What would this syntax look like? I read somewhere that introducing closures in java is a bigger change than generic was in java 5. Is this true? pros and cons? (By now we definitely know that closures not will be included in the next Java release) OR edit: http://puredanger.com/tech/2009/11/18/closures-after-all/ :D edit2: Re-thinking JDK7: http://blogs.oracle.com/mr/entry

in Java 7 we have o.hashCode(); Objects.hashCode(o); Objects.hash(o); The first 2 are roughly the same with the null point check, but what is last one? When a single object reference is supplied, the returned value does not equal the hash code of that object reference. Why is that? I mean, we don't need 3 methods that do the same thing, I understand that, but why do we need Objects.hash() at all? When would you chose to use one vs another? Tim S. See the documentation for hashCode and hash . hash takes Object... while hashCode takes Object . The example given is: @Override public int hashCode(