java-7

I upgraded jdk to version 7_45. After compiling and executing the jar, which works fine, i packed it into an application bundle. But unfortunately i get this error message "LSOpenURLsWithRole() failed with error -10810 for the file /Users/.../MyApp.app". The same problem with the jdk 8 Early Access. I also. tried different setting in the info.plist for the "JVMVersion" key Since the jar itself works fine, i could do a workaround by replacing the JavaApplicationStub with my own executable which simply would call "java -jar ./.../MyApp.jar". But not really sure if that is a proper way to fix

Given this example from the generics tutorial . List<String> list = new ArrayList<>(); list.add("A"); // The following statement should fail since addAll expects // Collection<? extends String> list.addAll(new ArrayList<>()); Why does the last line not compile, when it seems it should compile. The first line uses a very similar construct and compiles without a problem. Please explain elaborately. First of all: unless you're using Java 7 all of this will not work, because the diamond <> has only been introduced in that Java version. Also, this answer assumes that the reader understands the

We use some varargs functions and as we move to java 1.7 we are getting a strange unchecked warning. Function add in interface ICache public interface ICache<O> { void add(Object source, O... objects); } in an interface reports the error. ICache.java:18: warning: [unchecked] Possible heap pollution from parameterized vararg type O void add(Object source, O... objects); where O is a type-variable: O extends Object declared in interface ICache 1 warning O extends Object, as its generic cache class. I read the xlint warnings and we do compile with unchecked on, but http://docs.oracle.com/javase/7

I watched the Oracle OTN Virtual Event: Java SE and JavaFX 2.0 (28 Feb 2012) and while talking about the new diamond operator (that Map<String, List<String>> myMap = new HashMap<>(); thing) the speaker mentioned that it was not as simpleto implement than one might think, as it is not a simple token replacement. My question is why? Why can't be this implemented as simply taking the string from the variable's declaration and put it into the diamond operator? I didn't implement it either, so I can only guess. But usually the reason these things are more complex than they seem is that first

The following code compiles fine in Java 1.6 but fails to compile in Java 1.7. Why? The relevant part of the code is the reference to the private 'data' field. The reference is from within the same class in which the field is defined, and so seems legal. But it is happening via a generically-typed variable. This code - a stripped down example based on a class from an in-house library - worked in Java 1.6 but doesn't now in Java 1.7. I'm not asking how to work around this. I've already done that. I'm trying to find an explanation of why this doesn't work any more. Three possibilities come to