<?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: Managing Environment Specific Configuration with Seam</title>
	<atom:link href="http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/feed/" rel="self" type="application/rss+xml" />
	<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/</link>
	<description>Blog by a developer for a developer</description>
	<lastBuildDate>Tue, 24 Aug 2010 13:52:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jacob.orshalick</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-19833</link>
		<dc:creator>jacob.orshalick</dc:creator>
		<pubDate>Fri, 12 Mar 2010 17:08:52 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-19833</guid>
		<description>Awesome, thanks for posting that here Maciej!  I would recommend creating a JIRA issue for adding this to Seam.  It would be a great component to make it easy for people to incorporate reCaptcha.</description>
		<content:encoded><![CDATA[<p>Awesome, thanks for posting that here Maciej!  I would recommend creating a JIRA issue for adding this to Seam.  It would be a great component to make it easy for people to incorporate reCaptcha.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maciej</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-19828</link>
		<dc:creator>Maciej</dc:creator>
		<pubDate>Fri, 12 Mar 2010 13:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-19828</guid>
		<description>I am also a great fun of reCaptcha project and Jboss seam, so I tried to integrate them both. I described how to do this in a short &lt;a href=&quot;http://www.info-system.eu/bazawiedzy/37-java/86-integrate-seam-with-recaptcha&quot; title=&quot;recaptcha and seam integration&quot; rel=&quot;nofollow&quot;&gt;article &lt;/a&gt;. Task is not that difficult, but maybe someone will save time, by copy-pasting my code :). Please place your comments to the article here.</description>
		<content:encoded><![CDATA[<p>I am also a great fun of reCaptcha project and Jboss seam, so I tried to integrate them both. I described how to do this in a short <a href="http://www.info-system.eu/bazawiedzy/37-java/86-integrate-seam-with-recaptcha" title="recaptcha and seam integration" rel="nofollow">article </a>. Task is not that difficult, but maybe someone will save time, by copy-pasting my code <img src='http://solutionsfit.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . Please place your comments to the article here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jacob.orshalick</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-2078</link>
		<dc:creator>jacob.orshalick</dc:creator>
		<pubDate>Thu, 07 Aug 2008 03:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-2078</guid>
		<description>&lt;blockquote cite=&quot;disown&quot;&gt;On a side note, would the component be required to be a seam component, or would this work for @Service:s, MDB:s and EJB:s too?&lt;/blockquote&gt;

For this approach it would be required to be a Seam component, but as I&#039;m sure you are well aware it is quite easy to make EJBs Seam components ;)  Simply annotate them with @Name!</description>
		<content:encoded><![CDATA[<blockquote cite="disown"><p>On a side note, would the component be required to be a seam component, or would this work for @Service:s, MDB:s and EJB:s too?</p></blockquote>
<p>For this approach it would be required to be a Seam component, but as I&#8217;m sure you are well aware it is quite easy to make EJBs Seam components <img src='http://solutionsfit.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />   Simply annotate them with @Name!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: disown</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-2068</link>
		<dc:creator>disown</dc:creator>
		<pubDate>Tue, 05 Aug 2008 11:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-2068</guid>
		<description>Well, I have a Seam service that reads the property file and parses the parameters, setting them in the context. If I only knew this was possible through components.xml... :)

On a side note, would the component be required to be a seam component, or would this work for @Service:s, MDB:s and EJB:s too?</description>
		<content:encoded><![CDATA[<p>Well, I have a Seam service that reads the property file and parses the parameters, setting them in the context. If I only knew this was possible through components.xml&#8230; <img src='http://solutionsfit.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>On a side note, would the component be required to be a seam component, or would this work for @Service:s, MDB:s and EJB:s too?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-1967</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 23 Jul 2008 01:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-1967</guid>
		<description>I manage it by letting you do it. :)</description>
		<content:encoded><![CDATA[<p>I manage it by letting you do it. <img src='http://solutionsfit.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jacob.orshalick</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-1487</link>
		<dc:creator>jacob.orshalick</dc:creator>
		<pubDate>Thu, 19 Jun 2008 13:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-1487</guid>
		<description>No, the captcha being used on my blog site is &lt;a href=&quot;http://recaptcha.net/whyrecaptcha.html&quot; rel=&quot;nofollow&quot;&gt;reCAPTCHA&lt;/a&gt;.  I am a big fan of reCAPTCHA, very easy to use, and looks good.  Perhaps I&#039;ll post a blog entry on integrating reCAPCHA into a Seam application if there is interest.  The Java plugin can be found &lt;a href=&quot;http://code.google.com/p/recaptcha/downloads/list?q=label:java-Latest&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>No, the captcha being used on my blog site is <a href="http://recaptcha.net/whyrecaptcha.html" rel="nofollow">reCAPTCHA</a>.  I am a big fan of reCAPTCHA, very easy to use, and looks good.  Perhaps I&#8217;ll post a blog entry on integrating reCAPCHA into a Seam application if there is interest.  The Java plugin can be found <a href="http://code.google.com/p/recaptcha/downloads/list?q=label:java-Latest" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay Gupta</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-1486</link>
		<dc:creator>Ajay Gupta</dc:creator>
		<pubDate>Thu, 19 Jun 2008 12:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-1486</guid>
		<description>By the way, I do like the captcha ):=. Is this the custom Seam captcha you were talking about a few days ago?</description>
		<content:encoded><![CDATA[<p>By the way, I do like the captcha ):=. Is this the custom Seam captcha you were talking about a few days ago?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay Gupta</title>
		<link>http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/comment-page-1/#comment-1484</link>
		<dc:creator>Ajay Gupta</dc:creator>
		<pubDate>Thu, 19 Jun 2008 12:06:42 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-configuration-with-seam/#comment-1484</guid>
		<description>Jacob,

Good and very well-written article indeed.  I would suggest an alternative technique to adding the  (test, prod etc) prefix to name of each file and then putting all such files into a single folder. You could \instead create a separate folder for each  inside some root directory and then, put the  specific files inside the respective  folders.  For example, if test, prod are 2 environments, create 2 folders: test and prod. Copy test env version of components.properties to test folder and prod version of components.properties to prod folder and do the same for all other env specific files. That is it.  This approach makes the env-specific files very easy to navigate and browse.  With this, you can also associate permissions with files in a specific  by simply configuring the permissions on the respective  folder.  

Thanks</description>
		<content:encoded><![CDATA[<p>Jacob,</p>
<p>Good and very well-written article indeed.  I would suggest an alternative technique to adding the  (test, prod etc) prefix to name of each file and then putting all such files into a single folder. You could \instead create a separate folder for each  inside some root directory and then, put the  specific files inside the respective  folders.  For example, if test, prod are 2 environments, create 2 folders: test and prod. Copy test env version of components.properties to test folder and prod version of components.properties to prod folder and do the same for all other env specific files. That is it.  This approach makes the env-specific files very easy to navigate and browse.  With this, you can also associate permissions with files in a specific  by simply configuring the permissions on the respective  folder.  </p>
<p>Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
