Is CA Technologies licensed to distribute Oracle Java in our DevTest?
I think it is correct to say that in the “normal” or “supported” use of DevTest, there is no need for Oracle JDK in DevTest. Only JRE is needed and needs to be distributed.
Whenever, you use java statements in beanshell scripts then those statements are interpreted (late type binding) by beanshell they are not compiled through JDK and then executed.
Obviously, within your company as a practice you could decide to limit the lines of actual scripting inside a .vsm or .tst file and instead provide that functionality compiled and stored in a jar file. E.g. in Eclipse it might be easier to code and debug those lines of java. In that case you are developing and compiling some java outside of DevTest. Your custom jar file is then added to the HotDeploy directory or lib/shared directory or can be distributed but it is already compiled so still no JDK needed anymore.
Have a look at https://docops.ca.com/devtest-solutions/10-3/en/release-notes/third-party-acknowledgments. In the zip file from that doc page you find the attached pdf on Oracle JRE.
Sorry, but you mean the customer doesn't need to buy Oracle JDK for DevTest. The customer can use Oralce JDK in DevTest. right?
Danny is right. We deliver an Oracle jre with DevTest.
Is the question with respect to the recent Oracle announcement that they will start charging customers and software vendors for the incorporation of Java SE (both JDK and JRE) in certain circumstances, starting early next year? I think we need some kind of official announcement of compliance with Oracle's new Terms & Conditions, to avoid any awkward discussions with Oracle in the future.
Retrieving data ...