No, once product.conf gets created that's where the framework will look for the java home value. Possibly you can create a slnk pointing to the latest JDK (and somehow keep that updated when a new JDK installs), then reference the slnk in product.conf.
SQL Developer Team
It's what I thought as the last resort to this problem. However I don't really get it when you said "where the framework will look for the java home value". What if the "SetJavaHome" value is omitted? I tried and it refers to JDK 1.7. Where did it get the "default" JDK version from?
Where did it get the "default" JDK version from?
SQL Developer 4.0 attempts to find the JDK. For example...
Since 4.0 requires some minimum jdk1.7 version, perhaps jdk1.8 is ignored, or at least jdk1.7 is preferred if 1.7 & 1.8 are installed.