Thread: JavaSE or JavaEE?

Java SE stands for Java Standard Edition.
Java EE stands for Enterprise Edition.

Java SE also contains the Swing GUI collection libraries by default as long as the
correct JRE is installed along side it.
I have not used the EE myself, but from what I have heard, the EE version is a lot more
complex than SE, it contains databases and queries as well as standard functionality.

The best way to go is to start with SE if you are starting out with Java. It's very powerful for what it is, free
and it is what most colleges/universities use. A more experienced member might be able to give you more
information on Java EE.

Wishes Ada xx

I cannot give you a definite answer to that.
however, I did a bit of searching and this: https://netbeans.org/kb/docs/java/javase-deploy.html
Seems to have some good information about it. It does refer to the Netbeans IDE, but all distribution is done with packaging and the JAR.
As for the memory consumption - I have not heard of Swing being a RAM hog - thats new to me, but something worth looking into.
Hope that helps a little bit more

Wishes Ada xx

This all completely depends upon how you wish to organize/build your application. You can get by on just J2SE by having your application make calls directly to the database - this gives you a 2-tier client/server application. J2EE allows you to build your application up into an n-tier architecture, and in so doing can make an application more scalable and maintainable by separating the roles into their own tiers (eg presentation, business logic, data access, etc...). J2EE is built on top of J2SE, so a solid understanding of J2SE is recommended before diving into J2EE.

from what i read swing comsumes more memory than the SWT

Curious where you read this (and this is just me, but I wouldn't base my decision solely on this)...both SWT and Swing have advantages/disadvantages - a quick google will let you be better informed on your choice (for instance, http://stackoverflow.com/questions/2...n-swt-vs-swing ). A big factor you may wish to consider is you're client base - if working on many different platforms using SWT will require you to distribute a version for each different platform.