1 Reply Latest reply on Feb 1, 2011 7:23 AM by safarmer

    EE SDK in Desktop Application


      I've been using Java for a couple of years and it seems that the SE (Desktop Edition) and EE (Enteprise/Server Edition) doesn't necessarily apply. The name can be a some what misleading thinking that you only can use SE if you want to develop desktop applications. I've recently found out that you can use, for example, JPA in a desktop application. This said, wouldn't it be better to change the naming from SE, EE to something that relates more to the type of application you want to develop? Simply calling it the Java Development Platform and within this platform you can use any sort of apis to develop desktop, web, mobile etc. In my opinion MSDN does a great job at this.

      Looking forward to your comments.

      Edited by: user13478995 on Jan 26, 2011 1:19 PM
        • 1. Re: EE SDK in Desktop Application
          One way to look at it is Java SE is the base JRE and Java EE is a set up libraries and specifications on top of the standard JRE. Java EE is just a specification and JPA is a part of this spec. You can download the SDK that gives you the interfaces to build against, but you then need an implementation to run your application.

          I think the bigest drawback to bundling them all together is that you are then adding things to the platform that many developers will not need. There is no point adding all of the interfaces for the complete Java EE specification for a Swing application. Also it would mean you are tied to a given version of Java EE or Java SE.

          I think the separation is good as it allows you to combine the components you require and even specific versions of a component or specification.

          Maybe I am just rambling so I will leave it at that for now :)