<?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: Solution using Seam to pagination issue with JSF on DataModel updates</title>
	<atom:link href="http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/feed/" rel="self" type="application/rss+xml" />
	<link>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/</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/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/comment-page-1/#comment-296</link>
		<dc:creator>jacob.orshalick</dc:creator>
		<pubDate>Sat, 08 Mar 2008 14:18:24 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/#comment-296</guid>
		<description>Thanks for the comment Andy!

Yes, this is certainly another option, but I thought it was a nice example (outside of the usual auditing, logging, security, etc) to demonstrate using stereotypes and get others thinking.  As you mention, you could always abstract the repeated JSF invocation out to some helper method and invoke it in a refresh(), but that&#039;s just not quite as exciting ;)</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Andy!</p>
<p>Yes, this is certainly another option, but I thought it was a nice example (outside of the usual auditing, logging, security, etc) to demonstrate using stereotypes and get others thinking.  As you mention, you could always abstract the repeated JSF invocation out to some helper method and invoke it in a refresh(), but that&#8217;s just not quite as exciting <img src='http://solutionsfit.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Gibson</title>
		<link>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/comment-page-1/#comment-293</link>
		<dc:creator>Andy Gibson</dc:creator>
		<pubDate>Sat, 08 Mar 2008 05:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/#comment-293</guid>
		<description>Why not just have a refresh() method that resets the results and the position. Since you are re-performing the search why not make the index reset a part of the research?

However, it is a great example on the power of creating your own stereotypes and using annotations/interceptors to neatly solve problems.</description>
		<content:encoded><![CDATA[<p>Why not just have a refresh() method that resets the results and the position. Since you are re-performing the search why not make the index reset a part of the research?</p>
<p>However, it is a great example on the power of creating your own stereotypes and using annotations/interceptors to neatly solve problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jacob.orshalick</title>
		<link>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/comment-page-1/#comment-105</link>
		<dc:creator>jacob.orshalick</dc:creator>
		<pubDate>Tue, 29 Jan 2008 14:51:01 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/#comment-105</guid>
		<description>No, it is simply required that the &lt;code&gt;@DataModel&lt;/code&gt; be available from the context (i.e. PAGE or CONVERSATION).  So if you wanted to make &lt;code&gt;myAction @Stateless&lt;/code&gt;, just make sure you outject to the appropriate context and you will be all set.</description>
		<content:encoded><![CDATA[<p>No, it is simply required that the <code>@DataModel</code> be available from the context (i.e. PAGE or CONVERSATION).  So if you wanted to make <code>myAction @Stateless</code>, just make sure you outject to the appropriate context and you will be all set.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lsabin</title>
		<link>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/comment-page-1/#comment-104</link>
		<dc:creator>lsabin</dc:creator>
		<pubDate>Tue, 29 Jan 2008 08:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/#comment-104</guid>
		<description>Wonderful idea. 
Just a question: is it needed that the component  &#039;myAction&#039; be @Stateful?</description>
		<content:encoded><![CDATA[<p>Wonderful idea.<br />
Just a question: is it needed that the component  &#8216;myAction&#8217; be @Stateful?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: koenhandekyn</title>
		<link>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/comment-page-1/#comment-45</link>
		<dc:creator>koenhandekyn</dc:creator>
		<pubDate>Thu, 20 Dec 2007 08:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/#comment-45</guid>
		<description>great article !! it solved the problem in a breeze !!!!</description>
		<content:encoded><![CDATA[<p>great article !! it solved the problem in a breeze !!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
