<?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: Configuration Properties Screencast</title>
	<atom:link href="http://blog.springsource.org/2009/09/11/configuration-properties-screencast/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.springsource.org/2009/09/11/configuration-properties-screencast/</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: dm Console Demo Screencast &#124; SpringSource Team Blog</title>
		<link>http://blog.springsource.org/2009/09/11/configuration-properties-screencast/comment-page-1/#comment-168930</link>
		<dc:creator>dm Console Demo Screencast &#124; SpringSource Team Blog</dc:creator>
		<pubDate>Wed, 21 Oct 2009 17:07:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2779#comment-168930</guid>
		<description>[...] Posted on October 21st, 2009 by Chris Frost in OSGi, dm Server.  Here is a screencast showing the dm Console for the dm Server. It gives a brief tour of the dm Console and then shows some of the features by deploying a simple demo application. The application consists of a configuration file, a web bundle and a content bundle. When deployed the application simply shows the contents of the configuration file in a web browser. The application is installed in parts for the purpose of this demo, in reality you would group the application together with either a &#039;par&#039; or a &#039;plan&#039;, to see how this is done with a &#039;plan&#039; file another screencast is available here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Posted on October 21st, 2009 by Chris Frost in OSGi, dm Server.  Here is a screencast showing the dm Console for the dm Server. It gives a brief tour of the dm Console and then shows some of the features by deploying a simple demo application. The application consists of a configuration file, a web bundle and a content bundle. When deployed the application simply shows the contents of the configuration file in a web browser. The application is installed in parts for the purpose of this demo, in reality you would group the application together with either a &#39;par&#39; or a &#39;plan&#39;, to see how this is done with a &#39;plan&#39; file another screencast is available here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jack</title>
		<link>http://blog.springsource.org/2009/09/11/configuration-properties-screencast/comment-page-1/#comment-168446</link>
		<dc:creator>jack</dc:creator>
		<pubDate>Sat, 12 Sep 2009 10:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2779#comment-168446</guid>
		<description>Very informative post. Thanks for the Configuration Properties Screencast.
&lt;a href=&quot;http://www.ccnaexams.com&quot; rel=&quot;nofollow&quot;&gt;ccna practice exams&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Very informative post. Thanks for the Configuration Properties Screencast.<br />
<a href="http://www.ccnaexams.com" rel="nofollow">ccna practice exams</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spowell</title>
		<link>http://blog.springsource.org/2009/09/11/configuration-properties-screencast/comment-page-1/#comment-168440</link>
		<dc:creator>spowell</dc:creator>
		<pubDate>Fri, 11 Sep 2009 16:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2779#comment-168440</guid>
		<description>@Marc, this would indeed be nice. Since the artefact meta-data is &lt;em&gt;discovered&lt;/em&gt; (when dropping the properties file into pickup or into the watched repository) at present the version defaults to zero. There is no standard unintrusive place to put meta-data in the properties file at the moment. There is no reason why more detailed meta-data (including version information) cannot be associated with the artefact when being placed in a repository programmatically, and publish and retract interfaces are under discussion.

Extensions to artefact references in plans are being designed as we type and we should see some further possibilities soon. If you have good ideas in this area, we would be delighted to hear your contributions.</description>
		<content:encoded><![CDATA[<p>@Marc, this would indeed be nice. Since the artefact meta-data is <em>discovered</em> (when dropping the properties file into pickup or into the watched repository) at present the version defaults to zero. There is no standard unintrusive place to put meta-data in the properties file at the moment. There is no reason why more detailed meta-data (including version information) cannot be associated with the artefact when being placed in a repository programmatically, and publish and retract interfaces are under discussion.</p>
<p>Extensions to artefact references in plans are being designed as we type and we should see some further possibilities soon. If you have good ideas in this area, we would be delighted to hear your contributions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://blog.springsource.org/2009/09/11/configuration-properties-screencast/comment-page-1/#comment-168439</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Fri, 11 Sep 2009 14:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springsource.com/?p=2779#comment-168439</guid>
		<description>Nice, I&#039;d love to see a versioning feature of the hot deployed properties file. As far as I can see the properties definition in the plan specifies any version (version=&quot;0&quot;).</description>
		<content:encoded><![CDATA[<p>Nice, I&#039;d love to see a versioning feature of the hot deployed properties file. As far as I can see the properties definition in the plan specifies any version (version=&#034;0&#034;).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

