If I embed the GPL 2 Java applet in my web application, should I free the source of the web application?

Suppose I'm working on a web application that has significant proprietary code written in JavaScript / HTML / etc.

Suppose further that there is a GPL v2 Java application that has some related functionality that I would like to offer my users when I deploy my application to various client sites.

So, I plan to convert a Java application to a Java applet and embed it in my web application. My web application will not directly call any functions of the applet, just using the basic functions of the browser to launch it in a specific place on a specific page.

Does this mean “work based on the Program” in terms of the GPL (or “binding” used in the FAQ ), so now I have to release all my original JavaScript / HTML code under the GPL? *

If so, does this mean that every HTML page that the GPL'd applet is embedded in must also be licensed in the GPL, with source sources? (Consider PHP web applications!)

Or, is the “simple aggregation” applet being implemented in the sense that I simply point out some related but independent functions?

Finally, will using Java Web Start launch the original Java application? If so, why?

(* Naturally, I will distribute the sources of the Java applet itself.)

+4
source share
2 answers

A really interesting scenario ... I think that any Java code that you modify is part of the actual applet, should be distributed, but it should be good to use, since it is spawned as a separate object, and you can save your HTML code / JS (although people already have this code if they can view it)

I see your script since HTML / JS is a script that runs a program that has GPL code. This is normal, and the script does not need to be issued, but something inside what is being launched should be distributed. Just my 2c - I can be very wrong.

+1
source

I think you are at legal risk if you do. I assume that in this case your application will be designed to freeze the applet and without it will work without it. You are actually embedding parts of your application in an applet that you also distribute to customers along with your web pages. There is a slight chance that your application is considered derivative, which will lead either to a violation of the GPL or to an extension of the license for your entire application. I would not do that.

+1
source

All Articles