<?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: Oracle Contributing Oracle Application Server Integration Code to Spring Framework</title>
	<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/</link>
	<description>The voice of SpringSource</description>
	<pubDate>Thu, 21 Aug 2008 01:38:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Interface21 Team Blog &#187; Spring Framework Certified on WebSphere</title>
		<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-28655</link>
		<pubDate>Thu, 21 Jun 2007 09:21:53 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-28655</guid>
					<description>[...] Fortunately, a solution is at hand to allow Spring to maximize the potential of the underlying platform. Spring provides a transaction abstraction&#8211;PlatformTransactionManager&#8211;that is semantically more complete than JTA but makes no assumptions about its environment. It&#39;s a key example of what we call portable service abstractions. Normally you don&#39;t use the PlatformTransactionManager directly, because Spring&#39;s declarative transaction management gives you a uniquely powerful option for applying programmatic transactions to any POJO, but it is the foundation of both programmatic and declarative transaction management in Spring. Because we don&#39;t make any assumptions about the environment, and environmental details don&#39;t leak into your code and decrease portability, we can safely tie into platform specifics. We&#39;ve done this for WebLogic, Oracle have done it for OC4J, and we have now worked with IBM to produce a first-class integration for WebSphere. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Fortunately, a solution is at hand to allow Spring to maximize the potential of the underlying platform. Spring provides a transaction abstraction&#8211;PlatformTransactionManager&#8211;that is semantically more complete than JTA but makes no assumptions about its environment. It&#39;s a key example of what we call portable service abstractions. Normally you don&#39;t use the PlatformTransactionManager directly, because Spring&#39;s declarative transaction management gives you a uniquely powerful option for applying programmatic transactions to any POJO, but it is the foundation of both programmatic and declarative transaction management in Spring. Because we don&#39;t make any assumptions about the environment, and environmental details don&#39;t leak into your code and decrease portability, we can safely tie into platform specifics. We&#39;ve done this for WebLogic, Oracle have done it for OC4J, and we have now worked with IBM to produce a first-class integration for WebSphere. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: The thoughts of an IT professional : Competition in transaction semantics</title>
		<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-15610</link>
		<pubDate>Tue, 13 Mar 2007 15:59:15 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-15610</guid>
					<description>[...] I was reading this post by Rod Johnson on the Interface 21 blog about Oracle Application Server and Spring when I came across this quote: Because Spring provides a rich, portable transaction abstraction, it does the work under the covers of driving JTA and other APIs, so your code doesn&#8217;t need to know anything about the underlying infrastructure, and thus can take advantage of any proprietary APIs that give more control or greater efficiency. Spring supports both declarative and programmatic transactions, so you can layer transaction management onto POJOs that don&#8217;t know anything about it; or, if transaction management is part of your business logic, you can use a more elegant API that offers more features than JTA (*), isn&#8217;t tied to JNDI, and is much less verbose to work with. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I was reading this post by Rod Johnson on the Interface 21 blog about Oracle Application Server and Spring when I came across this quote: Because Spring provides a rich, portable transaction abstraction, it does the work under the covers of driving JTA and other APIs, so your code doesn&#039;t need to know anything about the underlying infrastructure, and thus can take advantage of any proprietary APIs that give more control or greater efficiency. Spring supports both declarative and programmatic transactions, so you can layer transaction management onto POJOs that don&#039;t know anything about it; or, if transaction management is part of your business logic, you can use a more elegant API that offers more features than JTA (*), isn&#039;t tied to JNDI, and is much less verbose to work with. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Cheat Codes &#187; Oracle Contributing Oracle Application Server Integration Code to &#8230;</title>
		<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-14538</link>
		<pubDate>Mon, 05 Mar 2007 23:42:51 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-14538</guid>
					<description>[...] Original post by Rod Johnson and powered by Img Fly [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Original post by Rod Johnson and powered by Img Fly [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Vinny Carpenter&#8217;s blog &#187; Daily del.icio.us for Feb 28, 2007 through Mar 01, 2007</title>
		<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-14019</link>
		<pubDate>Sat, 03 Mar 2007 01:49:36 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-14019</guid>
					<description>[...] Interface21 Team Blog - Oracle Contributing Oracle Application Server Integration Code to Spring Framework - This is similar to what we have with WebLogic 8.1 and above in WebLogicJtaTransactionManager. The OC4JJtaTransactionManager should be used in place of the generic JtaTransactionManager in an OC4J environment, and provides the following benefits [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Interface21 Team Blog - Oracle Contributing Oracle Application Server Integration Code to Spring Framework - This is similar to what we have with WebLogic 8.1 and above in WebLogicJtaTransactionManager. The OC4JJtaTransactionManager should be used in place of the generic JtaTransactionManager in an OC4J environment, and provides the following benefits [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: James Governor&#8217;s Monkchips &#187; links for 2007-03-02</title>
		<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-14010</link>
		<pubDate>Fri, 02 Mar 2007 23:27:29 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-14010</guid>
					<description>[...] Interface21 Team Blog » Oracle Contributing Oracle Application Server Integration Code to Spring Framework holy open source interfaces. Rod Johnson is changing the industry one app server vendor at a time. Spring Rules. First BEA shitcans its own componentry in favour of Spring. Now Oracle too. I can see Rod on a plane to Somers sometime soon. Seriously GREAT (tags: Interface21 Spring RodJohnson POJO SCA SOA Oracle) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Interface21 Team Blog » Oracle Contributing Oracle Application Server Integration Code to Spring Framework holy open source interfaces. Rod Johnson is changing the industry one app server vendor at a time. Spring Rules. First BEA shitcans its own componentry in favour of Spring. Now Oracle too. I can see Rod on a plane to Somers sometime soon. Seriously GREAT (tags: Interface21 Spring RodJohnson POJO SCA SOA Oracle) [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Email Server Online &#187; Blog Archive &#187; Oracle Contributing Oracle Application Server Integration Code to &#8230;</title>
		<link>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-13642</link>
		<pubDate>Wed, 28 Feb 2007 05:28:16 +0000</pubDate>
		<guid>http://blog.springsource.com/main/2007/02/27/oracle-contributing-oracle-application-server-integration-code-to-spring-framework/#comment-13642</guid>
					<description>[...] Original post by Rod Johnson and a wordpress plugin by Elliott [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Original post by Rod Johnson and a wordpress plugin by Elliott [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
