Another aspect I thought of would be say installing the SQL Net drivers on a desktop, for connecting to the Oracle database on a server. Last I remember (last year when I got a new desktop), the only way to install the client software was through the Oracle Universal Installer (OUI), which is java-based as well.
So does this mean changes will coming down the road whereby all client installations will have to either be separately licensed, or will various IT groups have to remove all client software and force the developers, testers, etc to log directly onto the server, and then run their client software on the server?
Clear directives from Oracle on ALL of the aspects and implications of the new licensing scheme are woefully inadequate. I've been Googling and conducting other searches trying to find definitive answers, to no avail. The best I was able to find was:
(https://www.oracle.com/technetwork/java/javaseproducts/overview/javasesubscriptionfaq-4891443.html) at the bottom, clearly states:
If I use another Oracle product that relies on the Oracle Java SE runtime, how will a Java SE Subscription affect me?
If you use any Oracle product that requires Java SE, you are already licensed to use the Oracle Java SE runtime with, and for the sole purpose of running, that Oracle product. Java SE Subscription provides licensing and support if you need to use the Oracle Java SE runtime for running products not licensed by Oracle. For more information see My.Oracle.Support Note 1557737.1 - (Support Entitlement for Java SE When Used As Part of Another Oracle Product – Requires Support Login).
But even this doesn't explain the implications for client software.
Thanks for any clarification on this. It seems like all of this would have been talked about and thoroughly hashed out well before any final decision was made and all appropriate documentation was updated correctly to reflect all of the various issues and scenarios. Oracle used to be great at this. What's happened?