If I embed a GPL 2 Java applet into my web app, do I have to release the web app source?

Question

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

Suppose further, there exists a GPL v2 Java application that has some related functionality I'd like to offer my users, when I deploy my app to various customer sites.

So I plan to convert the Java application to a Java applet, and embed it into my web application. My web application would not be directly calling any functions of the applet, just using basic browser functionality to launch it in a particular space on a particular page.

Does this constitute "a work based on the Program" in terms of the GPL (or "linking" as used in the FAQ), such that I am now obligated to release all of my original JavaScript/HTML code under the GPL?^*

If so, doesn't this mean that every HTML page that embeds a GPL'd applet must also be licensed under the GPL, with original sources provided? (Consider PHP web apps!)

Or, is embedding an applet "mere aggregation" in the sense that I'm just pointing to some related, but independent functionality?

Finally, would using Java Web Start to launch the original Java application change anything? If so, why?

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

Answer 1

Really interesting scenario... I think any Java code you modify that is part of the actual applet needs to be distributed, but it should be ok to use it since it is spawned as a separate entity and you can keep your HTML/JS proprietary (though people already have that code if they can view source it)

I see your scenario as the HTML/JS being a script that launches a program that has GPL code in it. It's fine to do that and the script doesn't need to be released, but anything inside what is being launched needs to be distributed. Just my 2c - I could be very wrong.

Answer 2

I think you are taking a legal risk if you do this. I suppose in this case your application would be designed to depend on an applet and would lack functionality without it. You are in effect implementing parts of your application in the applet, which you also distribute to the clients along with your webpages. There is a not-insignificant chance that your application is considered a derived work, leading either to GPL violation or extending the license to your whole application. I wouldn't do it.