J2SE vs J2EE

[rutski89]

I'm extremely confused about the differences between J2SE and
J2EE. I definitely get the idea that J2EE is meant of developing
multitier robust applications, web services, and other such fancy
enterprise level software. What I don't understand is why this
can't be done in plain old J2SE?

I hear things like "because J2EE includes special packages such
as java.sql and javax.sql", yet I see that I have those classes
available in J2SE as well.

In sort my question is:
What can J2EE do that J2SE can't? ***and why***?

 

[Lothar Kimmeringer]

I hear things like "because J2EE includes special packages such
as java.sql and javax.sql", yet I see that I have those classes
available in J2SE as well.

In sort my question is:
What can J2EE do that J2SE can't? ***and why***?

J2EE is based on J2SE, so the question is hard to answer, because
if you like you can implement everything that is in J2EE yourself.

J2EE is a framework that combines all the things you need for
enterprise-orientated applications. So things like EJB, JNDI,
the JavaMail- and Activation-Framework are put together. You
can also use the single parts of the J2EE framework separately
(like JavaMail) but to make sure that your application is running
on all systems you have to make sure for yourself, that all the
systems will use the JavaMail-framework of a specific version.

J2EE defines exactly what version of JavaMail, ... is used with
J2EE Version 1, 2, 3, ... so just with saying "this version of
GreatApplication" uses J2EE Version 1.4 it's only one thing to
check to make sure that all the single parts of the J2EE-framework
you're using is compatible to the one being installed.


Regards, Lothar
--
Lothar Kimmeringer E-Mail: (e-mail address removed)
PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

Always remember: The answer is forty-two, there can only be wrong
questions!

 

[Mark Space]

In sort my question is:
What can J2EE do that J2SE can't? ***and why***?

I don't know, specifically, but in general J2SE does everything most
people need. J2EE has some extra features that support Sun's concept of
enterprise (business and big business) applications.

So if you are a developer using Sun products and methods, use J2EE.
Everyone else uses J2SE. If you don't know or aren't sure, use J2SE.

You might want to look for some Sun enterprise software and note which
ones require J2EE. That's the direction Sun's business software is going.

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

I don't know, specifically, but in general J2SE does everything most
people need. J2EE has some extra features that support Sun's concept of
enterprise (business and big business) applications.

So if you are a developer using Sun products and methods, use J2EE.
Everyone else uses J2SE. If you don't know or aren't sure, use J2SE.

You might want to look for some Sun enterprise software and note which
ones require J2EE. That's the direction Sun's business software is going.

This is completely wrong.

SUN have somewhat invented J2EE (like all other Java).

But the big player in the J2EE space is not SUN, but
IBM and BEA (and to some extent JBoss).

Arne

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

I'm extremely confused about the differences between J2SE and
J2EE. I definitely get the idea that J2EE is meant of developing
multitier robust applications, web services, and other such fancy
enterprise level software. What I don't understand is why this
can't be done in plain old J2SE?

I hear things like "because J2EE includes special packages such
as java.sql and javax.sql", yet I see that I have those classes
available in J2SE as well.

In sort my question is:
What can J2EE do that J2SE can't? ***and why***?

J2SE defines:
Java language
Java virtual machine
Java libraries

J2EE defines:
servlet
JSP
EJB
JCA
(+ some minor specs)

J2EE requires J2SE.

You will always need J2SE.

You will need J2EE if you want to use any of the
features in J2EE.

Most server Java code actually uses J2EE (RMI and
socket servers are not that common).

Arne

PS: After the latest confusing name change I think it is JSE and JEE.

 

[John O'Conner]

PS: After the latest confusing name change I think it is JSE and JEE.

Yes, the renaming can be confusing. However, the current naming
convention as of today is this:
* Java SE (Java Platform, Standard Edition)
* Java EE (Java Platform, Enterprise Edition)

Regards,
John O'Conner

 

[Mark Space]

J2EE defines:
servlet
JSP

Tomcat requires J2SE, not J2EE. This is quite well stated on the latest
Tomcat page.

We might be talking somewhat at cross purposes here. I think the
original poster is referring to the download objects, not a spec.

 

[rutski89]

Thank you all for your replies. It's all becoming clear to me now.
After much digging I found these two page on the web:

http://java.sun.com/javaee/5/docs/api/
http://java.sun.com/javaee/5/docs/tutorial/doc/

I have a relatively clear picture of what J2EE after looking at those
pages, and reading over all of your replies to my original post

--Patrick

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Tomcat requires J2SE, not J2EE. This is quite well stated on the latest
Tomcat page.

We might be talking somewhat at cross purposes here. I think the
original poster is referring to the download objects, not a spec.

Tomcat requires the parts of J2EE that it uses.

It comes with the Tomcat distribution.

And in that sense Tomcat are very similar to application servers
supporting the full J2EE stack.

They do usually not require the J2EE SDK either.

Arne