<?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>AMIS Technology blog &#187; client side</title>
	<atom:link href="http://technology.amis.nl/blog/tag/client-side/feed" rel="self" type="application/rss+xml" />
	<link>http://technology.amis.nl/blog</link>
	<description>Weblog for the AMIS Technology corner</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:34:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ADF 11g &#8211; implementing conditionally required input fields &#8211; by playing client side hide and seek</title>
		<link>http://technology.amis.nl/blog/6716/adf-11g-implementing-conditionally-required-input-fields-by-playing-client-side-hide-and-seek</link>
		<comments>http://technology.amis.nl/blog/6716/adf-11g-implementing-conditionally-required-input-fields-by-playing-client-side-hide-and-seek#comments</comments>
		<pubDate>Thu, 17 Dec 2009 12:17:49 +0000</pubDate>
		<dc:creator>Lucas Jellema</dc:creator>
				<category><![CDATA[ADF & JHeadstart]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[adf 11g]]></category>
		<category><![CDATA[client side]]></category>
		<category><![CDATA[clientListener]]></category>
		<category><![CDATA[ppr]]></category>
		<category><![CDATA[required]]></category>
		<category><![CDATA[rich client components]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=6716</guid>
		<description><![CDATA[
	The requirement I was dealing with today in ADF 11g Rich Client Components was the following: we have an input field that is required under certain conditions. Only when one of this cluster of fields has a value, is it required. Otherwise it is optional. The use case was that the fields represent a detail [...]]]></description>
		<wfw:commentRss>http://technology.amis.nl/blog/6716/adf-11g-implementing-conditionally-required-input-fields-by-playing-client-side-hide-and-seek/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>ADF 11g &#8211; Extend and Override standard client side behavior by manipulating the Javascript prototype</title>
		<link>http://technology.amis.nl/blog/6630/adf-11g-extend-and-override-standard-client-side-behavior-by-manipulating-the-javascript-prototype</link>
		<comments>http://technology.amis.nl/blog/6630/adf-11g-extend-and-override-standard-client-side-behavior-by-manipulating-the-javascript-prototype#comments</comments>
		<pubDate>Tue, 08 Dec 2009 09:58:05 +0000</pubDate>
		<dc:creator>Lucas Jellema</dc:creator>
				<category><![CDATA[ADF & JHeadstart]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[adf 11g]]></category>
		<category><![CDATA[client side]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[rich client]]></category>
		<category><![CDATA[validations]]></category>

		<guid isPermaLink="false">http://technology.amis.nl/blog/?p=6630</guid>
		<description><![CDATA[
	This article describes a way to extend and override the standard behavior of ADF client side JavaScript libraries. In this particular case we needed to learn about the client side validation errors in order to feed our expertise manager: when the user submits the form, client side validations are performed and when errors are found, [...]]]></description>
		<wfw:commentRss>http://technology.amis.nl/blog/6630/adf-11g-extend-and-override-standard-client-side-behavior-by-manipulating-the-javascript-prototype/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

