<?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: Code samples from SpringOne &#039;Beyond the obvious&#039; talk</title>
	<atom:link href="http://blog.springsource.org/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.org/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/</link>
	<description>The voice of SpringSource</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:31:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Christian</title>
		<link>http://blog.springsource.org/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/comment-page-1/#comment-175716</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Wed, 01 Sep 2010 11:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.interface21.com/main/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/#comment-175716</guid>
		<description>Do you know, that the Cocoon Project people have done something similar? They even support merging property Files for the PropertyPlaceholderConfigurer.

Take a look at:
http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/2.0/1304_1_1.html

cya</description>
		<content:encoded><![CDATA[<p>Do you know, that the Cocoon Project people have done something similar? They even support merging property Files for the PropertyPlaceholderConfigurer.</p>
<p>Take a look at:<br />
<a href="http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/2.0/1304_1_1.html" rel="nofollow">http://cocoon.apache.org/subprojects/configuration/1.0/spring-configurator/2.0/1304_1_1.html</a></p>
<p>cya</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loading environment specific spring configurations. &#124; deNoo's blog</title>
		<link>http://blog.springsource.org/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/comment-page-1/#comment-169559</link>
		<dc:creator>Loading environment specific spring configurations. &#124; deNoo's blog</dc:creator>
		<pubDate>Thu, 19 Nov 2009 12:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.interface21.com/main/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/#comment-169559</guid>
		<description>[...] Such a solution was first introduced in the FIRM application many years ago  I&#8217;ve also described some solutions (incl. one that&#8217;s very similar to yours) in this blog post: http://blog.springsource.com/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Such a solution was first introduced in the FIRM application many years ago  I&#039;ve also described some solutions (incl. one that&#039;s very similar to yours) in this blog post: <a href="http://blog.springsource.com/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/" rel="nofollow">http://blog.springsource.com/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://blog.springsource.org/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/comment-page-1/#comment-38351</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Tue, 07 Aug 2007 04:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.interface21.com/main/2007/06/25/code-samples-from-springone-beyond-the-obvious-talk/#comment-38351</guid>
		<description>We did something similar at our company, except that we already have an enterprise solution for properties which vary between environments. So what we ended up doing was having various style of development environments, exclusively for use with local development on one&#039;s workstation. Instead of a system property, we used a property file located in the user&#039;s home directory to key the bean ref context ID of the appropriate application context. This allowed our developers to turn off all infrastructure-related code and focus entirely on developing their individual components.</description>
		<content:encoded><![CDATA[<p>We did something similar at our company, except that we already have an enterprise solution for properties which vary between environments. So what we ended up doing was having various style of development environments, exclusively for use with local development on one&#039;s workstation. Instead of a system property, we used a property file located in the user&#039;s home directory to key the bean ref context ID of the appropriate application context. This allowed our developers to turn off all infrastructure-related code and focus entirely on developing their individual components.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

