I’m running Designer Release 9.0.1FP10 SHF81 and am having an issue with the Java Compliance setting not working or sticking after a client restart.
I need to compile this specific project with Java 1.8 but I’m not 100% sure it is? No matter where I attempt to set the compliance level, it reverts back to 1.5 after I re-open it.
If I open a java agent or library and choose “Enable project specific settings” then select 1.8, it all looks good but if I then look at the Agent or Library “Properties” under the $JavaCompilerSource or $JavaCompilerTarget fields they show 1.5 or 1.6?
I’ve found a few references from years back regarding similar issues but no real resolution?
I need be sure this is compiled with 1.8 to use TLS1.2 or our application will stop working at the end of the month.
Subject: I will say, we’ve run into similar issues.
I’m not sure what the real answer is, unfortunately. We had enough trouble with it to experiment heavily, so heavily we’re not sure what actually caused the problem to settle down.
Subject: I’ll find out…
Well I’ll find out next week if its actually compiling against JRE 1.8 when the API endpoint I’m connecting to stops supporting TLS1.0!
I’m encouraged by the fact that any Notes Clients prior to 9.0.1 FP10 started complaining about java version compatibility when trying to run the newly compiled code. I just have to ensure that each time I open the Designer client that I go it the preferences and reset the default compliance to 1.8 from 1.5 before I edit any code. A bit of an annoyance!
Subject: I will say, we’ve run into similar issues.
I’m not sure what the real answer is, unfortunately. We had enough trouble with it to experiment heavily, so heavily we’re not sure what actually caused the problem to settle down.
Subject: Did it actually compile against JRE 1.8?
Was wondering what your results were on this. Did JRE 1.8 work and give you TLS 1.2?