J2EE or Tomcat

[itpcl]

From the job market newspaper, there are many jobs about J2EE.
However Apache Tomcat has many tools to add on.
I am thinking of learning to use an application server.
Which one should I choose?

Thanks

 

[Sudsy]

From the job market newspaper, there are many jobs about J2EE.
However Apache Tomcat has many tools to add on.
I am thinking of learning to use an application server.
Which one should I choose?

Thanks

Tomcat is a servlet container, not a full J2EE implementation.
Do some more reading on the differences.

 

[itpcl]

Tomcat is a servlet container, not a full J2EE implementation.
Do some more reading on the differences.

I can make a war file and put to webapps directory of Tomcat and J2EE.
Both Tomcat and J2EE accept war file (even a bit difference),
a servlet program can display on both Tomcat and J2EE.

As I am trying to learn more servlet and try to deploy as war file,
both Apache Tomcat and Sun J2ee can do it.
Which one is better choice?

 

[Sender]

Go for J2EE if you want EJB. Go for the simpler Tomcat if you don't. In
fact, most people who want java go for both.

 

[Sudsy]

I can make a war file and put to webapps directory of Tomcat and J2EE.
Both Tomcat and J2EE accept war file (even a bit difference),
a servlet program can display on both Tomcat and J2EE.

As I am trying to learn more servlet and try to deploy as war file,
both Apache Tomcat and Sun J2ee can do it.
Which one is better choice?

If it's just wars then either will do and Tomcat is easier to
configure. If you graduate to using ears then J2EE is going to
be the only choice. OTOH, early exposure to the complexities
of a J2EE server will pay off if you ever start using EJBs.
So the answer, as usual, is "it depends".

 

[Juha Laiho]

(e-mail address removed) (itpcl) said:

I can make a war file and put to webapps directory of Tomcat and J2EE.
Both Tomcat and J2EE accept war file (even a bit difference),
a servlet program can display on both Tomcat and J2EE.

How about reading on what there is in J2EE that is not in Tomcat.

J2EE is a toolset for larger variety of situations that Tomcat, but
then, J2EE being as large as it is can easily be overkill for some
things that are a good match for Tomcat. So, there are applications
for which Tomcat is more suitable, and applications for which J2EE
is more suitable. Also the development organisation makes a difference;
there are organisational structures that lessen the value of some
benefits of J2EE, and are better suitable for the Tomcat model of
development.

 

[itpcl]

there are applications

for which Tomcat is more suitable, and applications for which J2EE
is more suitable.

If I want to learn Cocoon, EJB and XML, which server is better?