Linked by Thom Holwerda on Mon 18th Jul 2005 16:21 UTC, submitted by anonymous
Permalink for comment 5843
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-06
Nothing against Ruby on Rails. Exciting project.
But, there seems to be this continuing misnomer that conflates Java Servlets and JSP with overarching J2EE.
Servlets and JSP are subcomponents of J2EE. Servlet containers like Tomcat are simply that -- servlet containers. Containers that implement a mere portion of the entirety of what J2EE (now simply JEE) is.
If this were titled "Ruby on Rails and Struts", I wouldn't even be making this point, but J2EE, as most are well aware, is far bigger than simply the servlet portion.
Is writing a personal web blog tool leveraging all of the J2EE stack overkill vs something like a simpler RoR or Struts application? Yes. But that's because they server different purposes.
Web based applications CAN BE part of much larger sets of infrastructure, so its nice to be able to more easily integrate such applications into larger systems. If your application doesn't need that kind of integration, then the common web only style frameworks and infrastructure are more than adequate.
I do not know, but I do not believe that Ruby has a similar back end architecture of the scope of all of JEE.