<?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>Java Code Geeks &#187; Oleg Varaksin</title> <atom:link href="http://www.javacodegeeks.com/author/Oleg-Varaksin/feed" rel="self" type="application/rss+xml" /><link>http://www.javacodegeeks.com</link> <description>Java 2 Java Developers Resource Center</description> <lastBuildDate>Fri, 24 May 2013 19:00:57 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.5.1</generator> <item><title>JSF: choice between legacy components and fashionable performance killers</title><link>http://www.javacodegeeks.com/2013/05/jsf-choice-between-legacy-components-and-fashionable-performance-killers.html</link> <comments>http://www.javacodegeeks.com/2013/05/jsf-choice-between-legacy-components-and-fashionable-performance-killers.html#comments</comments> <pubDate>Thu, 09 May 2013 20:23:43 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=12575</guid> <description><![CDATA[This blog post was originated due to performance issues in one big web application. Everybody optimizes Java code, but it seems nobody try to optimize the JavaScript code. Strange, because on the client-side there is much room for improvements. I would state, even more than on the server-side. We will analyse the perfomance of editable [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/05/jsf-choice-between-legacy-components-and-fashionable-performance-killers.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Passing complex objects in URL parameters</title><link>http://www.javacodegeeks.com/2013/03/passing-complex-objects-in-url-parameters.html</link> <comments>http://www.javacodegeeks.com/2013/03/passing-complex-objects-in-url-parameters.html#comments</comments> <pubDate>Tue, 19 Mar 2013 11:00:23 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category> <category><![CDATA[JSON]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=10026</guid> <description><![CDATA[Imagine you would like to pass primitive data types, complex Java objects like java.util.Data, java.lang.List, generic classes, arrays and everything what you want via URL parameters in order to preset default values on any web page after the page was loaded. Common task? Yeah, but available solutions are mostly restricted to encoding / decoding of [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/03/passing-complex-objects-in-url-parameters.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>JSF &#8211; Eager CDI beans</title><link>http://www.javacodegeeks.com/2013/02/jsf-eager-cdi-beans.html</link> <comments>http://www.javacodegeeks.com/2013/02/jsf-eager-cdi-beans.html#comments</comments> <pubDate>Tue, 19 Feb 2013 20:00:45 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[CDI]]></category> <category><![CDATA[JSF]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=8815</guid> <description><![CDATA[Everybody knows eager managed beans in JSF 2. @ManagedBean has an eager attribute. If eager=&#8217;true&#8217; and the scope is application, then this bean must be created when the application starts and not during the first reference to the bean. This is a nice feature when you want to load application scoped data (e.g. some select [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/02/jsf-eager-cdi-beans.html/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>GET / POST with RESTful Client API</title><link>http://www.javacodegeeks.com/2013/01/get-post-with-restful-client-api.html</link> <comments>http://www.javacodegeeks.com/2013/01/get-post-with-restful-client-api.html#comments</comments> <pubDate>Tue, 01 Jan 2013 08:25:01 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category> <category><![CDATA[PrimeFaces]]></category> <category><![CDATA[RESTful Web Services]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=6367</guid> <description><![CDATA[There are many stuff in the internet how to work with RESTful Client API. These are basics. But even though the subject seems to be trivial, there are hurdles, especially for beginners. In this post I will try to summarize my know-how, how I did this in real projects. I usually use Jersey (reference implementation [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/01/get-post-with-restful-client-api.html/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Configure timeout for CDI conversations</title><link>http://www.javacodegeeks.com/2012/09/configure-timeout-for-cdi-conversations.html</link> <comments>http://www.javacodegeeks.com/2012/09/configure-timeout-for-cdi-conversations.html#comments</comments> <pubDate>Tue, 18 Sep 2012 22:00:00 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[Apache MyFaces]]></category> <category><![CDATA[CDI]]></category> <category><![CDATA[JSF]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/configure-timeout-for-cdi-conversations.html</guid> <description><![CDATA[CDI conversation scope is a nice feature when developing JSF applications. Imagine you have large data tables which take a long time to be loaded. You normally don&#8217;t want to place the loaded data in session scoped beans by reason of high memory consumption. And you can&#8217;t place the loaded data in view scoped beans [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/09/configure-timeout-for-cdi-conversations.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>JSF Event-based communication: New-school approach</title><link>http://www.javacodegeeks.com/2012/07/jsf-event-based-communication-new.html</link> <comments>http://www.javacodegeeks.com/2012/07/jsf-event-based-communication-new.html#comments</comments> <pubDate>Mon, 23 Jul 2012 10:00:00 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/jsf-event-based-communication-new-school-approach.html</guid> <description><![CDATA[In the last post, we learnt event-based communication on basis of Observer / Event Listener and Mediator patterns. Due to their shortcomings I would like to show more efficient ways for event-based communication. We will start with Google Guava EventBus and end up with CDI (Contexts and Dependency Injection for the Java EE platform). Guava [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/07/jsf-event-based-communication-new.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>JSF Event-based communication: Old-school approach</title><link>http://www.javacodegeeks.com/2012/07/jsf-event-based-communication-old.html</link> <comments>http://www.javacodegeeks.com/2012/07/jsf-event-based-communication-old.html#comments</comments> <pubDate>Tue, 17 Jul 2012 01:00:00 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/jsf-event-based-communication-old-school-approach.html</guid> <description><![CDATA[Web applications written in JSF consist of beans which interact among each other. Communication between beans is one of the main design patterns when developing a web application. Sometimes, one bean need to send events to other beans to inform them about some changes or whatever else. We can normally inject a managed or Spring [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/07/jsf-event-based-communication-old.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Dynamic forms, JSF world was long waiting for</title><link>http://www.javacodegeeks.com/2012/06/dynamic-forms-jsf-world-was-long.html</link> <comments>http://www.javacodegeeks.com/2012/06/dynamic-forms-jsf-world-was-long.html#comments</comments> <pubDate>Fri, 15 Jun 2012 19:00:00 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category> <category><![CDATA[PrimeFaces]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/dynamic-forms-jsf-world-was-long-waiting-for.html</guid> <description><![CDATA[The new PrimeFaces Extensions release 0.5.0 brought a new DynaForm component. Normally, we can build a form quite straightforward by h:panelGrid oder p:panelGrid if the count of rows / columns, positions of elements, etc. are known. That&#8217;s true for static forms. But it&#8217;s not possible to use h:panelGrid oder p:panelGrid if a form is described [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/06/dynamic-forms-jsf-world-was-long.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Custom JSF validator for required fields</title><link>http://www.javacodegeeks.com/2012/05/custom-jsf-validator-for-required.html</link> <comments>http://www.javacodegeeks.com/2012/05/custom-jsf-validator-for-required.html#comments</comments> <pubDate>Tue, 29 May 2012 10:00:00 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Enterprise Java]]></category> <category><![CDATA[JSF]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/custom-jsf-validator-for-required-fields.html</guid> <description><![CDATA[JSF components implementing EditableValueHolder interface have two attributes &#8216; required&#8217; and &#8216; requiredMessage&#8217; &#8211; a flag indicating that the user is required to input / select not empty value and a text for validation message. We can use that, but it&#8217;s not flexible enough, we can&#8217;t parameterize the message directly in view (facelets or jsp) [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/05/custom-jsf-validator-for-required.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>High Performance Webapps &#8211; Data URIs</title><link>http://www.javacodegeeks.com/2012/04/high-performance-webapps-data-uris.html</link> <comments>http://www.javacodegeeks.com/2012/04/high-performance-webapps-data-uris.html#comments</comments> <pubDate>Thu, 26 Apr 2012 09:00:00 +0000</pubDate> <dc:creator>Oleg Varaksin</dc:creator> <category><![CDATA[Software Development]]></category> <category><![CDATA[Performance]]></category> <category><![CDATA[Scalability]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/2012/10/high-performance-webapps-data-uris.html</guid> <description><![CDATA[I continue to write tips for perfomance optimization of websites. The last post was about jQuery objects. This post is about data URIs. Data URIs are an interesting concept on the Web. Read &#8221; Data URIs explained&#8221; please if you don&#8217;t know what it does mean. Data URIs are a technique for embedding resources as [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/04/high-performance-webapps-data-uris.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 2/4 queries in 0.001 seconds using apc
Object Caching 1135/1136 objects using apc
Content Delivery Network via jcg.javacodegeeks.netdna-cdn.com

Served from: www.javacodegeeks.com @ 2013-05-25 10:58:10 -->