<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>solutionsfit.com &#124; Jacob Orshalick &#187; JBoss Rich Faces</title>
	<atom:link href="http://solutionsfit.com/blog/category/java/jsf/jboss-rich-faces/feed/" rel="self" type="application/rss+xml" />
	<link>http://solutionsfit.com/blog</link>
	<description>Blog by a developer for a developer</description>
	<lastBuildDate>Sat, 31 Jul 2010 01:39:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Solution using Seam to pagination issue with JSF on DataModel updates</title>
		<link>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/</link>
		<comments>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/#comments</comments>
		<pubDate>Tue, 13 Nov 2007 17:53:53 +0000</pubDate>
		<dc:creator>jacob.orshalick</dc:creator>
				<category><![CDATA[JBoss Rich Faces]]></category>
		<category><![CDATA[JBoss Seam]]></category>
		<category><![CDATA[JSF]]></category>

		<guid isPermaLink="false">http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/</guid>
		<description><![CDATA[In an implementation using the JBoss RichFaces rich:dataScroller component, I noticed the first attribute of a UIData component is maintained even if the DataModel it is displaying has changed. It turns out, this is an issue with JSF. The UIData component does not track the DataModel it represents. Thus, when the DataModel is updated it [...]]]></description>
		<wfw:commentRss>http://solutionsfit.com/blog/2007/11/13/solution-using-seam-to-pagination-issue-with-jsf-on-datamodel-updates/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Alleviating client-side back-button issues with Ajax4JSF and RichFaces</title>
		<link>http://solutionsfit.com/blog/2007/11/08/alleviating-client-side-back-button-issues-with-ajax4jsf-and-richfaces/</link>
		<comments>http://solutionsfit.com/blog/2007/11/08/alleviating-client-side-back-button-issues-with-ajax4jsf-and-richfaces/#comments</comments>
		<pubDate>Thu, 08 Nov 2007 19:52:40 +0000</pubDate>
		<dc:creator>jacob.orshalick</dc:creator>
				<category><![CDATA[JBoss Ajax4JSF]]></category>
		<category><![CDATA[JBoss Rich Faces]]></category>
		<category><![CDATA[JBoss Seam]]></category>

		<guid isPermaLink="false">http://solutionsfit.com/blog/?p=4</guid>
		<description><![CDATA[Recently an article I wrote was published on the Seam conversation model and how issues with the back-button can be eliminated through a continuation approach.  This aids developers in resolving back-button issues with respect to server-side state, but what about the client-side.  Ajax development is a breeze with Seam especially when used in [...]]]></description>
		<wfw:commentRss>http://solutionsfit.com/blog/2007/11/08/alleviating-client-side-back-button-issues-with-ajax4jsf-and-richfaces/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
	</channel>
</rss>
