Comments on: Is it a Tomcat, or the Elephant in the Room? http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/ The voice of SpringSource Sun, 20 Jul 2008 22:42:19 +0000 http://wordpress.org/?v=2.0.11 by: SpringSource Team Blog » The Biggest Loser's Next Contestant: Java Bloatware http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-102709 Thu, 10 Apr 2008 01:29:10 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-102709 [...] The future of enterprise Java is becoming clear. The morbidly obese legacy platforms are in decline, with leaner solutions increasingly used in production as well as in development. Legacy technologies such as EJB are becoming less and less relevant.The lukewarm takeup of Java EE 5 leaves it looking increasingly like the last gasp of traditional J2EE bloatware. Meanwhile, the Java EE 6 specification is finally set to allow for greater modularity, in a radical change which will have important implications for developers and is likely to rejuvenate competition among implementations. As the standards and the products based upon them have gathered pound after pound of cellulite, SOA, Web 2.0 and other infrastructural changes continually impose new requirements that were not foreseen when J2EE was conceived a decade ago, as a chubby but cute baby. [...] […] The future of enterprise Java is becoming clear. The morbidly obese legacy platforms are in decline, with leaner solutions increasingly used in production as well as in development. Legacy technologies such as EJB are becoming less and less relevant.The lukewarm takeup of Java EE 5 leaves it looking increasingly like the last gasp of traditional J2EE bloatware. Meanwhile, the Java EE 6 specification is finally set to allow for greater modularity, in a radical change which will have important implications for developers and is likely to rejuvenate competition among implementations. As the standards and the products based upon them have gathered pound after pound of cellulite, SOA, Web 2.0 and other infrastructural changes continually impose new requirements that were not foreseen when J2EE was conceived a decade ago, as a chubby but cute baby. […]

]]> by: Java Pro News » Blog Archive » Tomcat Could Displace JBoss in Some JBoss Deployments http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-96867 Tue, 05 Feb 2008 15:16:53 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-96867 [...] On a side note, anyone reading Rod’s blog recently will notice something that I’m sure the JBoss team has. Rod is very positive about Tomcat and, to a degree, questions whether Tomcat could displace JBoss in a non-insignificant portion of JBoss deployments. While SpringSource intends to support leading app servers including JBoss, it appears that coopetition is coming to a Tomcat/Spring/JBoss user near you! [...] […] On a side note, anyone reading Rod’s blog recently will notice something that I’m sure the JBoss team has. Rod is very positive about Tomcat and, to a degree, questions whether Tomcat could displace JBoss in a non-insignificant portion of JBoss deployments. While SpringSource intends to support leading app servers including JBoss, it appears that coopetition is coming to a Tomcat/Spring/JBoss user near you! […]

]]> by: An update on SpringSource « rand($thoughts); http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-96701 Tue, 05 Feb 2008 04:59:58 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-96701 [...] On a side note, anyone reading Rod’s blog recently will notice something that I’m sure the JBoss team has. Rod is very positive about Tomcat and, to a degree, questions whether Tomcat could displace JBoss in a non-insignificant portion of JBoss deployments. While SpringSource intends to support leading app servers including JBoss, it appears that coopetition is coming to a Tomcat/Spring/JBoss user near you! [...] […] On a side note, anyone reading Rod's blog recently will notice something that I'm sure the JBoss team has. Rod is very positive about Tomcat and, to a degree, questions whether Tomcat could displace JBoss in a non-insignificant portion of JBoss deployments. While SpringSource intends to support leading app servers including JBoss, it appears that coopetition is coming to a Tomcat/Spring/JBoss user near you! […]

]]> by: openBlog » Open Source War? Spring+Tomcat vs Jboss http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-94619 Wed, 30 Jan 2008 05:53:58 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-94619 [...] As you may know, SpringSource acquired Covalent, the company that has been providing Apache support for more than 10 years. Clearly, SpringSource goes for the Spring + Tomcat strategy. [...] […] As you may know, SpringSource acquired Covalent, the company that has been providing Apache support for more than 10 years. Clearly, SpringSource goes for the Spring + Tomcat strategy. […]

]]> by: Yuval Goldstein http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-93848 Mon, 28 Jan 2008 10:21:34 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-93848 My 2 Cents: - Distributed transactions across machines are not that widely used. Actually, even if I have the technical ability to do them, I would suggest a more loosely coupled aproach such as explicitly using compensating actions even without having the supporting built-in infrastructure. So the bottom line here that Tomcat is still fine, :) - JTA transactions across database actions and JMS actions is a very nice feature, but if you are aiming at just doing simple stuff asynchronously you may even settle for the concurrency utils. In my opinion this is what makes the real difference between full blown JEE and tomcat. Yuval Goldstein My 2 Cents:

- Distributed transactions across machines are not that widely used.
Actually, even if I have the technical ability to do them, I would suggest a more loosely coupled aproach such as explicitly using compensating actions even without having the supporting built-in infrastructure.
So the bottom line here that Tomcat is still fine, :)

- JTA transactions across database actions and JMS actions is a very nice feature, but if you are aiming at just doing simple stuff asynchronously you may even settle for the concurrency utils. In my opinion this is what makes the real difference between full blown JEE and tomcat.

Yuval Goldstein

]]> by: SpringSource Team Blog » Spring Overtakes EJB as a Skills Requirement http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-91912 Thu, 24 Jan 2008 00:04:54 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-91912 [...] Moving away from EJB provides greater architectural flexibility, at a time when requirements are changing, through the rise of SOA and other forces, and companies are increasingly choosing lighter-weight deployment platforms. Although support for various parts of the EJB 3.0 model is available outside a full-blown application server (including in Spring 2.5, which offers the EJB 3.0 DI model in addition to its own, and in Pitchfork, which is used as the basis of WebLogic 10's EJB 3.0 implementation), EJB is a component model fundamentally predicated on deployment to a traditional application server. [...] […] Moving away from EJB provides greater architectural flexibility, at a time when requirements are changing, through the rise of SOA and other forces, and companies are increasingly choosing lighter-weight deployment platforms. Although support for various parts of the EJB 3.0 model is available outside a full-blown application server (including in Spring 2.5, which offers the EJB 3.0 DI model in addition to its own, and in Pitchfork, which is used as the basis of WebLogic 10's EJB 3.0 implementation), EJB is a component model fundamentally predicated on deployment to a traditional application server. […]

]]> by: sat http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-88927 Wed, 16 Jan 2008 20:37:19 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-88927 Jeenvan, I'm sorry to say that it looks stupid to post your error msg here and ask for help. Use common sense. Go to some Spring Forum and post it. Jeenvan,
I'm sorry to say that it looks stupid to post your error msg here and ask for help. Use common sense. Go to some Spring Forum and post it.

]]> by: Revue de Presse Xebia par J2EE, Agilité et SOA : Le blog de Xebia France http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-88208 Mon, 14 Jan 2008 17:12:07 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-88208 [...] Les serveurs J2EE commerciaux comme open source rencontrent aujourd’hui un nouveau type de concurrence : les simples moteurs de servlet comme Tomcat (cf Is it a Tomcat, or the Elephant in the Room? par Rod Johnson, fondateur de Spring Framework). [...] […] Les serveurs J2EE commerciaux comme open source rencontrent aujourd'hui un nouveau type de concurrence : les simples moteurs de servlet comme Tomcat (cf Is it a Tomcat, or the Elephant in the Room? par Rod Johnson, fondateur de Spring Framework). […]

]]> by: SpringSource Team Blog » Happy Birthday Tony Hoare http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-88166 Mon, 14 Jan 2008 12:58:04 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-88166 [...] That was earlier this century–and was the legacy of concepts from last century. Today, things are different–at least in the enterprise Java space. The dramatic growth in the popularity of Tomcat is perhaps the biggest proof point for the fact that developers now have the power to enforce simplicity. The (healthy) pressure of Ruby on Rails on Java (which I think will ultimately strengthen Java) points to the same thing. There's even evidence that some of the traditional application server vendors understand the change and how it can benefit their customers. BEA, through embracing Spring and other technologies that simplify customer experience, have arguably led the way. Even Sun–with the Java EE 6 Profile concept–seem to be moving with the times, and acknowledging the reality that many customers no longer want a traditional, monolithic application server. [...] […] That was earlier this century–and was the legacy of concepts from last century. Today, things are different–at least in the enterprise Java space. The dramatic growth in the popularity of Tomcat is perhaps the biggest proof point for the fact that developers now have the power to enforce simplicity. The (healthy) pressure of Ruby on Rails on Java (which I think will ultimately strengthen Java) points to the same thing. There's even evidence that some of the traditional application server vendors understand the change and how it can benefit their customers. BEA, through embracing Spring and other technologies that simplify customer experience, have arguably led the way. Even Sun–with the Java EE 6 Profile concept–seem to be moving with the times, and acknowledging the reality that many customers no longer want a traditional, monolithic application server. […]

]]> by: Jeevan Edakkunnath Mana http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-86131 Tue, 08 Jan 2008 15:18:02 +0000 http://blog.springsource.com/main/2007/12/24/is-it-a-tomcat-or-the-elephant-in-the-room/#comment-86131 Hi Rod, I am Jeevan Edakkunnath Mana ,a j2ee developer from India. I am not sending reply to your Blog.I dont know whether I can directly send a request like this.. I am very new to Spring Frame work.I have gone through several pdf and tutorial regarding Spring Applications.I was trying to do some web applications with Spring 2.5 in NetBeans 5.5 with Sun Java System Application Server 9.0 as Application Server.I am not getting the correct Controller program logic. I am facing a problem in binding the form variables with the bean. The exception am getting is given below. javax.servlet.jsp.JspTagException: Neither BindingResult nor plain target object for bean name 'backingObject' available as request attribute at org.springframework.web.servlet.tags.BindTag.doStartTagInternal(BindTag.java:120) at org.springframework.web.servlet.tags.RequestContextAwareTag.doStartTag(RequestContextAwareTag.java:77) at org.apache.jsp.index_jsp._jspService(index_jsp.java:89) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:353) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:412) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:318) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) I posted the problem in spring forums also.But i am not getting the proper solution. I am expecting your very valuable reply on this regard,as am not able to move further.If am getting solved this problem,i can go ahead with Spring frame work Hibernate integration application.If you want i will send you the code wich i have developed for this application. I will be very thank ful to you for any kind of help. Thanking you. Jeevan Edakkunnath Mana, Miracle Software Systems,Vizag India. Hi Rod,
I am Jeevan Edakkunnath Mana ,a j2ee developer from India.
I am not sending reply to your Blog.I dont know whether I can directly send a request like this..
I am very new to Spring Frame work.I have gone through several pdf and tutorial regarding Spring Applications.I was trying to do some web applications with Spring 2.5 in NetBeans 5.5 with Sun Java System Application Server 9.0 as Application Server.I am not getting the correct Controller program logic. I am facing a problem in binding the form variables with the bean.
The exception am getting is given below.
javax.servlet.jsp.JspTagException: Neither BindingResult nor plain target object for bean name 'backingObject' available as request attribute
at org.springframework.web.servlet.tags.BindTag.doStartTagInternal(BindTag.java:120)
at org.springframework.web.servlet.tags.RequestContextAwareTag.doStartTag(RequestContextAwareTag.java:77)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:89)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:353)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:412)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:318)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
I posted the problem in spring forums also.But i am not getting the proper solution.
I am expecting your very valuable reply on this regard,as am not able to move further.If am getting solved this problem,i can go ahead with Spring frame work Hibernate integration application.If you want i will send you the code wich i have developed for this application.
I will be very thank ful to you for any kind of help.
Thanking you.
Jeevan Edakkunnath Mana,
Miracle Software Systems,Vizag
India.

]]>