Red Hat will grow beyond its Linux roots next week and sell a subscription service supporting an open-source Java application server, according to people familiar with the company’s plans.
Red Hat to serve Java
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Sounds like fun.
On a side not, I hope JOnAS and Geronimo can find a way to convince Sun’s legal department that Sun’s redistribution-prohibiting notice Sun made them put up is unnecessary.
cheers,
dalibor topic
You could package both as just an install option.
no?
What’s an application server? Is it just a Java VM?
What’s an application server? Is it just a Java VM?
—–
its a j2ee implementation
example: tomcat, jonas, jboss, websphere, sun j2ee. it can run jsp pages
Can’t hurt to give JBoss, Sun, and IBM a little more competition. The bundling effect alone (aka, “let’s use the Red Hat solution!”) should give RH a nice foot in the market.
-Erwos
An application server includes an Enterprise JavaBean container as well, which Tomcat lacks.
WebLogic, JBoss, Websphere, etc are J2EE application
servers. Tomcat is just a Java web server.
An application server includes an Enterprise JavaBean container as well, which Tomcat lacks.
——–
doesnt jakarta include that?
tomcat does servlets and jsps out of the box, but you can use openEJB if you want EJBs on tomcat. imho, you should use just enough j2ee that you can get away with, its not that hard to do an MVC framework for a mid sized webapp that just uses jsps with taglibs rather then the full jsp/servlet/ejb thing that sun recommends.
Jonas is the only contender against JBoss in open source J2EE application servers (Considering Apache Geronimo is still not available). However, you can make very capable J2EE applicatios without using those servers or EJB at all (Like using Spring and Servlet containers.)
Spring rocks !
http://www.springframework.org
People are realizing that EJBs are sheer overkill for most projects. It’s not every day that you land a contract for building an “airline reservation system” or anything of that magnitude. For all but the largest projects, a relatively simple and straightforward servlet/JDBC approach will more than suffice. Couple this with a framework like Spring, Struts or Tapestry and you can be very productive.
And for the large projects they are usually too slow, at least if we are talking EntityBeans with container based persistence.