<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Portability at the Framework Level</title>
	<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/</link>
	<description>The voice of SpringSource</description>
	<pubDate>Thu, 28 Aug 2008 10:29:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Web Applications and OSGi &#171; ITPassion</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-108607</link>
		<pubDate>Thu, 05 Jun 2008 11:07:59 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-108607</guid>
					<description>[...] Since the first milestones of Spring Dynamic Modules, requests for running web applications in OSGi started to come in. It has been probably one of the most requested features and no wonder, once 1.0 final was released, web support has been the main focus of the 1.1 branch. I am pleased to report that, with the just released M2, as already hinted by Juergen, Spring-DM supports not just vanilla wars (available since 1.1.0 M1) but also Spring-MVC applications running inside OSGi. In this entry, I would like to briefly discuss the typical OSGi web scenario and Spring-DM&#8217;s approach. But first, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Since the first milestones of Spring Dynamic Modules, requests for running web applications in OSGi started to come in. It has been probably one of the most requested features and no wonder, once 1.0 final was released, web support has been the main focus of the 1.1 branch. I am pleased to report that, with the just released M2, as already hinted by Juergen, Spring-DM supports not just vanilla wars (available since 1.1.0 M1) but also Spring-MVC applications running inside OSGi. In this entry, I would like to briefly discuss the typical OSGi web scenario and Spring-DM&#039;s approach. But first, [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: SpringSource Team Blog &#187; Portability, Fish and Chips</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-105817</link>
		<pubDate>Fri, 09 May 2008 22:33:43 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-105817</guid>
					<description>[...] Ian is exactly right. The SpringSource Application Platform is another choice for Spring deployment. Nothing has changed in the Spring Framework and Portfolio itself, which remains committed to portability. We look forward to continuing our work with folk like Ian to ensure the optimal experience in running Spring on WebSphere and every other popular platform. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Ian is exactly right. The SpringSource Application Platform is another choice for Spring deployment. Nothing has changed in the Spring Framework and Portfolio itself, which remains committed to portability. We look forward to continuing our work with folk like Ian to ensure the optimal experience in running Spring on WebSphere and every other popular platform. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: SpringSource Team Blog &#187; Today, Portability Matters More Than Ever</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104730</link>
		<pubDate>Tue, 29 Apr 2008 18:23:00 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104730</guid>
					<description>[...] Posted on April 29th, 2008 by Juergen Hoeller in Spring.  Yesterday, I blogged about how Spring helps maximize application portability. Even if the portability problem has been an ongoing topic in enterprise Java land for many years, that blog was timely. Today, Oracle announced that its $6.7 billion acquisition of BEA Systems has closed. There is substantial overlap between the product sets of the two companies, so this is bound to bring uncertainty to the WebLogic and OC4J customer bases. WebLogic and OC4J may both fall into the &#34;J2EE server&#34; category but they are very different products with very different characteristics. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Posted on April 29th, 2008 by Juergen Hoeller in Spring.  Yesterday, I blogged about how Spring helps maximize application portability. Even if the portability problem has been an ongoing topic in enterprise Java land for many years, that blog was timely. Today, Oracle announced that its $6.7 billion acquisition of BEA Systems has closed. There is substantial overlap between the product sets of the two companies, so this is bound to bring uncertainty to the WebLogic and OC4J customer bases. WebLogic and OC4J may both fall into the &#34;J2EE server&#34; category but they are very different products with very different characteristics. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: SpringSource Team Blog &#187; Web Applications and OSGi</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104728</link>
		<pubDate>Tue, 29 Apr 2008 17:45:38 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104728</guid>
					<description>[...] Posted on April 29th, 2008 by Costin Leau in Spring, Java, OSGi, 2.5/2.1.  Since the first milestones of Spring Dynamic Modules, requests for running web applications in OSGi started to come in. It has been probably one of the most requested features and no wonder, once 1.0 final was released, web support has been the main focus of the 1.1 branch. I am pleased to report that, with the just released M2, as already hinted by Juergen, Spring-DM supports not just vanilla wars (available since 1.1.0 M1) but also Spring-MVC applications running inside OSGi. In this entry, I would like to briefly discuss the typical OSGi web scenario and Spring-DM&#39;s approach. But first, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Posted on April 29th, 2008 by Costin Leau in Spring, Java, OSGi, 2.5/2.1.  Since the first milestones of Spring Dynamic Modules, requests for running web applications in OSGi started to come in. It has been probably one of the most requested features and no wonder, once 1.0 final was released, web support has been the main focus of the 1.1 branch. I am pleased to report that, with the just released M2, as already hinted by Juergen, Spring-DM supports not just vanilla wars (available since 1.1.0 M1) but also Spring-MVC applications running inside OSGi. In this entry, I would like to briefly discuss the typical OSGi web scenario and Spring-DM&#39;s approach. But first, [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dave</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104682</link>
		<pubDate>Tue, 29 Apr 2008 03:47:09 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104682</guid>
					<description>There is a patch for WL8.1 to support 1.4.</description>
		<content:encoded><![CDATA[<p>There is a patch for WL8.1 to support 1.4.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: links for 2008-04-29 &#187; SDLC Blog</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104676</link>
		<pubDate>Tue, 29 Apr 2008 02:32:33 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104676</guid>
					<description>[...] SpringSource Team Blog » Portability at the Framework Level Portability support in the Spring framework is a great feature. In most enterprises is also a key factor to avoid vendor lock-in and to allow easier migrations. (tags: springframework portability) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] SpringSource Team Blog » Portability at the Framework Level Portability support in the Spring framework is a great feature. In most enterprises is also a key factor to avoid vendor lock-in and to allow easier migrations. (tags: springframework portability) [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Juergen Hoeller</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104654</link>
		<pubDate>Mon, 28 Apr 2008 20:44:32 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104654</guid>
					<description>Hi Phil,

To the best of my knowledge, WebLogic 8.1 supports J2EE 1.3 only. This is also what BEA's reference documentation says: http://edocs.bea.com/wls/docs81/compatibility/compatibility.html

Juergen</description>
		<content:encoded><![CDATA[<p>Hi Phil,</p>
<p>To the best of my knowledge, WebLogic 8.1 supports J2EE 1.3 only. This is also what BEA&#039;s reference documentation says: <a href="http://edocs.bea.com/wls/docs81/compatibility/compatibility.html" rel="nofollow">http://edocs.bea.com/wls/docs81/compatibility/compatibility.html</a></p>
<p>Juergen
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Phil</title>
		<link>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104650</link>
		<pubDate>Mon, 28 Apr 2008 20:12:54 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2008/04/28/portability-at-the-framework-level/#comment-104650</guid>
					<description>Hi Juergen,

A minor correction: WebLogic 8.1 supports J2EE 1.4.

- Phil</description>
		<content:encoded><![CDATA[<p>Hi Juergen,</p>
<p>A minor correction: WebLogic 8.1 supports J2EE 1.4.</p>
<p>- Phil
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
