<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Enterprise Java and the American Motors Gremlin</title>
	<atom:link href="http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Fri, 19 Mar 2010 07:01:07 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SpringSource Launches Enterprise Java Cloud &#124; SpringSource Team Blog</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-168143</link>
		<dc:creator>SpringSource Launches Enterprise Java Cloud &#124; SpringSource Team Blog</dc:creator>
		<pubDate>Wed, 19 Aug 2009 09:55:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-168143</guid>
		<description>[...] initiative is a logical extension of our integrated Build/Run/Manage approach to unifying the application lifecycle, extending our vision of simplifying enterprise Java [...]</description>
		<content:encoded><![CDATA[<p>[...] initiative is a logical extension of our integrated Build/Run/Manage approach to unifying the application lifecycle, extending our vision of simplifying enterprise Java [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gargi S</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-167552</link>
		<dc:creator>Gargi S</dc:creator>
		<pubDate>Sat, 11 Jul 2009 17:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-167552</guid>
		<description>&gt; By solution, I mean providing out-of-the-box end-to-end web development framework - and improving constituents like the Spring Controllers hierarchy

I think, the main advantage of Spring is it&#039;s less invasive and pluggable. Choose what you like/consider best fit.

&gt;Instead of focusing on such bread-and-butter issues, so much energy is being expended on OSGi and Grails which are irrelevant for the typical java development project.

I believe Innovation can come from Grails that might help Java/Spring&#039;s cause. Those who use Spring want innovation, and it need to be written all in Java.

&gt; so yes, Spring could become the next J2EE

I don&#039;t totally share this concern. I&#039;m eager to see the next innovation for Spring. Also, you don&#039;t make major innovations, just about every other day, it takes time. To be fair, Spring in its current form is good enough and caters to the needs of application developers, and will most probably do so for some years to come.

Finally, today its Java and Spring, in the coming years it could be Grails and something else. As developers, we should just keep our minds open, and cultivate the ability to learn and absorb new ideas, regardless of the source.

History has proved that innovation, and solutions that really solve the needs have always been successful. Spring has been one of them. It would be interesting to see if they continue with it or someone else would take it from where they stop.

We live in interesting times. The next 2 years are surely going to be interesting for Java.</description>
		<content:encoded><![CDATA[<p>&gt; By solution, I mean providing out-of-the-box end-to-end web development framework &#8211; and improving constituents like the Spring Controllers hierarchy</p>
<p>I think, the main advantage of Spring is it&#039;s less invasive and pluggable. Choose what you like/consider best fit.</p>
<p>&gt;Instead of focusing on such bread-and-butter issues, so much energy is being expended on OSGi and Grails which are irrelevant for the typical java development project.</p>
<p>I believe Innovation can come from Grails that might help Java/Spring&#039;s cause. Those who use Spring want innovation, and it need to be written all in Java.</p>
<p>&gt; so yes, Spring could become the next J2EE</p>
<p>I don&#039;t totally share this concern. I&#039;m eager to see the next innovation for Spring. Also, you don&#039;t make major innovations, just about every other day, it takes time. To be fair, Spring in its current form is good enough and caters to the needs of application developers, and will most probably do so for some years to come.</p>
<p>Finally, today its Java and Spring, in the coming years it could be Grails and something else. As developers, we should just keep our minds open, and cultivate the ability to learn and absorb new ideas, regardless of the source.</p>
<p>History has proved that innovation, and solutions that really solve the needs have always been successful. Spring has been one of them. It would be interesting to see if they continue with it or someone else would take it from where they stop.</p>
<p>We live in interesting times. The next 2 years are surely going to be interesting for Java.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Hat Reacts to SpringSource&#39;s Leadership &#124; SpringSource Team Blog</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-167188</link>
		<dc:creator>Red Hat Reacts to SpringSource&#39;s Leadership &#124; SpringSource Team Blog</dc:creator>
		<pubDate>Wed, 03 Jun 2009 20:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-167188</guid>
		<description>[...] the customers I talk to also realize the best way to accelerate time to value is to pursue a joined up experience and vision that simplifies enterprise Java throughout the application lifecycle. This explains why SpringSource continues our leadership in the Build phase, with Grails, Spring [...]</description>
		<content:encoded><![CDATA[<p>[...] the customers I talk to also realize the best way to accelerate time to value is to pursue a joined up experience and vision that simplifies enterprise Java throughout the application lifecycle. This explains why SpringSource continues our leadership in the Build phase, with Grails, Spring [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SpringSource Acquires Hyperic &#124; Blogging Hyperic</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-166772</link>
		<dc:creator>SpringSource Acquires Hyperic &#124; Blogging Hyperic</dc:creator>
		<pubDate>Mon, 18 May 2009 18:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-166772</guid>
		<description>[...] Hyperic has been working hard to help tear down the brick wall that often exists between operations and development. In fact, we started this company because the founders (all developers) knew all too well how tough and distracting it was to be a developer called into firefighting situations (Backflip.com comes to mind&#8230;). We started by accepting the incredible responsibility of providing software that wakes ops people up when things inevitably go wrong. We soon realized that there was a bigger opportunity to provide products that help both developers and operations be successful. SpringSource&#8217;s acquisition of Hyperic enables us to seize this opportunity as one company. Rod &amp; the SpringSource team agree. [...]</description>
		<content:encoded><![CDATA[<p>[...] Hyperic has been working hard to help tear down the brick wall that often exists between operations and development. In fact, we started this company because the founders (all developers) knew all too well how tough and distracting it was to be a developer called into firefighting situations (Backflip.com comes to mind&#8230;). We started by accepting the incredible responsibility of providing software that wakes ops people up when things inevitably go wrong. We soon realized that there was a bigger opportunity to provide products that help both developers and operations be successful. SpringSource&#039;s acquisition of Hyperic enables us to seize this opportunity as one company. Rod &amp; the SpringSource team agree. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: V</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-166019</link>
		<dc:creator>V</dc:creator>
		<pubDate>Mon, 11 May 2009 13:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-166019</guid>
		<description>Hi, having just led a project for developing the first version of a new web Java EE based product, I could not agree more with Rod&#039;s diagnosis of what ails java development today.
But despite this clear vision of the problem, SpringSource has not been able to deliver a real solution in the last couple of years.  By solution, I mean providing out-of-the-box end-to-end web development framework - and improving constituents like the Spring Controllers hierarchy,(I believe deprecated in 3.0 now) adding support/tags for Ajax libraries like Dojo,  and providing good documentation and training.  For instance, there is almost no training provided in India, unbelievable!!  And detailed documentation on writing annotation based controllers is still wanted, for those who ventured into Spring MVC.  Instead of focusing on such bread-and-butter issues, so much energy is being expended on OSGi and Grails which are irrelevant for the typical java development project.  I guess Spring provides enough ammo to blow the enterprise complexity away, but learning to load and use its artillery is almost as complex - so yes, Spring could become the next J2EE! :(</description>
		<content:encoded><![CDATA[<p>Hi, having just led a project for developing the first version of a new web Java EE based product, I could not agree more with Rod&#039;s diagnosis of what ails java development today.<br />
But despite this clear vision of the problem, SpringSource has not been able to deliver a real solution in the last couple of years.  By solution, I mean providing out-of-the-box end-to-end web development framework &#8211; and improving constituents like the Spring Controllers hierarchy,(I believe deprecated in 3.0 now) adding support/tags for Ajax libraries like Dojo,  and providing good documentation and training.  For instance, there is almost no training provided in India, unbelievable!!  And detailed documentation on writing annotation based controllers is still wanted, for those who ventured into Spring MVC.  Instead of focusing on such bread-and-butter issues, so much energy is being expended on OSGi and Grails which are irrelevant for the typical java development project.  I guess Spring provides enough ammo to blow the enterprise complexity away, but learning to load and use its artillery is almost as complex &#8211; so yes, Spring could become the next J2EE! <img src='http://blog.springsource.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Enterprise Java: SpringSource Acquires Hyperic &#124; JAVA Developer&#39;s &#8230; Another java Blog</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-165352</link>
		<dc:creator>&#187; Enterprise Java: SpringSource Acquires Hyperic &#124; JAVA Developer&#39;s &#8230; Another java Blog</dc:creator>
		<pubDate>Tue, 05 May 2009 14:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-165352</guid>
		<description>[...] SpringSource Team Blog » Enterprise Java and the American Motors &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] SpringSource Team Blog » Enterprise Java and the American Motors &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: java Blog &#187; Enterprise Java: SpringSource Acquires Hyperic &#124; JAVA Developer&#39;s &#8230;</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-165348</link>
		<dc:creator>java Blog &#187; Enterprise Java: SpringSource Acquires Hyperic &#124; JAVA Developer&#39;s &#8230;</dc:creator>
		<pubDate>Tue, 05 May 2009 13:36:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-165348</guid>
		<description>[...] SpringSource Team Blog » Enterprise Java and the American Motors &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] SpringSource Team Blog » Enterprise Java and the American Motors &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SpringSource Team Blog &#187; SpringSource Plus Hyperic Unifies Application Lifecycle From Developer to Data Center</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-165260</link>
		<dc:creator>SpringSource Team Blog &#187; SpringSource Plus Hyperic Unifies Application Lifecycle From Developer to Data Center</dc:creator>
		<pubDate>Mon, 04 May 2009 14:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-165260</guid>
		<description>[...] on May 4th, 2009 by Rod Johnson in Spring.  A few weeks ago, I laid out SpringSource’s vision for creating a unified enterprise Java solution that spans the application lifecycle. Today, we announce a significant advance in realizing that [...]</description>
		<content:encoded><![CDATA[<p>[...] on May 4th, 2009 by Rod Johnson in Spring.  A few weeks ago, I laid out SpringSource’s vision for creating a unified enterprise Java solution that spans the application lifecycle. Today, we announce a significant advance in realizing that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-164705</link>
		<dc:creator>Grant</dc:creator>
		<pubDate>Tue, 28 Apr 2009 23:39:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-164705</guid>
		<description>Does anyone here have real world experience with Seam?  How much is this solving the productivity issue with Java based web app development?  Thanks.</description>
		<content:encoded><![CDATA[<p>Does anyone here have real world experience with Seam?  How much is this solving the productivity issue with Java based web app development?  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Topics about American-art &#187; Blog Archive &#187; Comment on Enterprise Java and the American Motors Gremlin by Topics&#8230;</title>
		<link>http://blog.springsource.com/2009/04/14/enterprise-java-and-the-american-motors-gremlin/comment-page-1/#comment-164115</link>
		<dc:creator>Topics about American-art &#187; Blog Archive &#187; Comment on Enterprise Java and the American Motors Gremlin by Topics&#8230;</dc:creator>
		<pubDate>Thu, 23 Apr 2009 01:21:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=1609#comment-164115</guid>
		<description>[...] Recorder and Times placed an observative post today on Comment on Enterprise Java and the American Motors Gremlin by Topics&#8230;Here&#8217;s a quick excerptJava and the American Motors Gremlin by RodHere&#8217;s a short outlineI pointed out that that was not the case, in view of the history of the Java&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Recorder and Times placed an observative post today on Comment on Enterprise Java and the American Motors Gremlin by Topics&#8230;Here&#039;s a quick excerptJava and the American Motors Gremlin by RodHere&#039;s a short outlineI pointed out that that was not the case, in view of the history of the Java&#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
