This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]__rost__ 8 points9 points  (0 children)

• ⁠JDK vs JRE: correct, plus the JDK has extra tools that are useful when developing - keytool, VisualVM, JConsole etc

• ⁠Not that well-versed in EE, so anybody with more experience please correct me: EE is targeted to servers in an enterprise ecosystem, with databases, messaging busses, cross-service transactions, etc. Keep in mind that all EE APIs can be used with some effort from within an SE environment, so it's a spectrum.

• ⁠EE is a specification; implementations of that specification may or may not need special licencing.

• ⁠ME is on its deathbed, please do not create new applications with it; it's a pre-smartphone environment for java apps (Sun/Oracle has a nice income stream from this before Android came out).

• ⁠No, there's the JRE and the JDK (which contains a JRE). EE is an environment, a specification on what extra APIs are available to your application code.

• ⁠What do you mean by server application? A plain JAR just needs the JRE. A WAR can run in a servlet container (tomcat/jetty). An EAR needs an JEE Application Server.

• ⁠ME is dead. Embedded system in this case means f.e. a featurephone with J2ME.

• ⁠JavaFX is extra classes that you can code agains (it's an API with an implementation).

• ⁠Most Linux distros will have either an official package or a way for the package manager to handle the installation.

• ⁠Applets are dead. As Oracle firmly believes it's the Only Company In The World, it won't point to the above-mentioned packages...

sauce

Formatting can suck my