Some working knowledge of J2EE or JSF is assumed for this article.

Like some of you I've been frustrated with this technology known as JSF or Java Server Faces. There are several different flavors out there that are built on the shoulders of JSF. For instance Oracle's ADF (Application Development Framework). Oracle ADF Faces Components is a set of over a 100 JSF components that let you build a richer user interface for your Java EE applications. Oracle ADF Faces also includes many of the framework features most needed by JSF developers today.

That is great, and in many ways it will make life easier to develop in a JSF environment. Some items you will find available in these "add on" packages have a real benefit. For instance, as of the date of this article, I was very surprised that a File Upload is a feature still not implemented in JSF in respect to using natural jsf tags. There are ways to accomplish this task in JSF but they are not native JSF approaches. The process is a "no brainer" in just about every other framework available today, including asp.net.

Another simple task (I thought) was having a data table present the results of a query in an editable format. Possibly to update a user record or shopping cart. After working in other technologies it was very efficient to return a result set to a data table object and let that object take care of some of the trivial behaviors and characteristics of the table itself. When I started exploring JSF I was frequently and at every turn becoming more and more frustrated in trying to duplicate some of the most basic of processes similar to managing records through data tables.

There are not a whole lot of resources out there yet on JSF although it is growing steadily, and I found that all too often the resources that I was finding on the internet either didn't apply to the more simple tasks or the information was just completely wrong. One example of that was that it was stated in one article I read that you cannot use command buttons inside of a JSF data table. The recommendation was to use JSF hyperlinks instead when trying to perform an action from a data table due to a bug in the framework that prevented command button actions to fire if the button resided inside of a data table.

At first I thought "you've got to be kidding me"! Then I remembered that I've been finding a fair amount of "bogus" information in regards to JSF development so I decided to do further research and discovered that information to be less than accurate as well.

I simply had to find a way to populate a data table through a result set and get a command button to fire an action and pass all of the data in the data table to the backing bean to update the record. Multiple command buttons would exist as well as hidden fields pertaining to id numbers and so forth. Pretty basic stuff and we've all done it before with relative ease.

It turned out that the solution was in fact a simple one. "Binding". You've heard about it and read about it. But this approach was something a little different as far as I could find.

Many of the blogs and articles that I read dealt with passing the values as parameters and following the steps to define the parameters in faces.config files etc., then retrieving the parameters in a backing bean. Processing the passed data required another set of procedures to utilize mapping to each of the field parameters passed and then processing could begin.

That seemed like a whole heck of a lot to me just to retrieve form data. Then it occurred to me that I should be able to "bind" a text field component on a page to a backing bean. Once it is bound then all I have to do is extract the data. And that's all there is to it. My query returned results and pre-populated a data table including text fields with the values of the query pre-populated in the text fields.

Each one of those text fields was bound to a "HtmlInputText" type in my backing bean. It was not a String type like other approaches define. Doing that does require you to map parameters and populate that String variable through your set methods once the form is submitted.

What I found is that if I bind my text field to a property of text field type that it solved my problem of passing values from a data table, and I didn't have to define parameter fields anywhere in any xml file. Now that I had that figured that out I needed to figure out how to get the value of that property that I've bound my form field to, well why not getValue()?

I personally hadn't seen any examples online or in books for retrieving the value from a form binding it to the type of form element it was and simply use the getValue() to pull out the value of the object. Used like this getParameterFromForm().getValue().

Let me clarify that I am NOT saying that trying this approach isn't documented anywhere, I find it hard to believe that I've had some stroke of genius that no one has had before in the world of java, especially since I'm coming from .NET and ColdFusion.

After doing that I no longer had any problems passing form data to my backing bean. I was able to dynamically populate data tables with any number of records including any number of command buttons within that data table and I didn't have to concern myself with remembering to define parameters in any other areas of the application.

So put simply you can bind your form fields to properties of the same type in your backing bean, and then extract the value of that object using getValue() if you prefer over utilizing parameter string mapping and similar approaches for processing form data. I found it to be easier and less time consuming which has costs associated to it as well.

With billions upon billions of people on the Earth and an estimated fifty seven million square miles of land, who would have thought that it would be possible to interact with virtually every single person from the comfort of your home or office. No, I'm not talking about talking to them over the phone or writing to them by mail but being able to interact with them via the Internet. Now more than ever, more and more people own computers with Internet connections and are surfing the web.

With billions of Internet users jumping from site to site, there will be those that will stumble upon your website. The question is, do you know anything about those website visitors? Are you getting detailed reports about your web visitors? If not, then as a webmaster you need to seek out the proper website visitor tracking software.

One that will be able to tell you everything about your visitors, like what they're doing when they visit your site or how long they are staying on your website? What links are they clicking? All these questions and more need to be answered. So if you are going to use a visitor tracking software, you might as well use the best. Provided by the advertising behemoth Google incorporated, Google Analytics is just the tool to use.

Google is a multi-billion dollar company that has resources to craft an excellent website visitor tracking software for all webmaster everywhere. This versatile services has an array of features including fast implementation, geo-targeting, customizable dashboards and more. The best part about Google Analytics is that its free. Any and every webmaster can afford the service. So if you are looking for a website visitor tracking software, I highly recommend Google Analytics.

If you are wondering why it is important to keep track of your website visitors, here are few reasons why. First, if you know important information like what your top exit pages are, then you can optimize those pages to preserve your traffic. Secondly, if you have ads on your website, you can use the site overlay feature to see what links your visitors tend to click on the most and reposition those links and place ads there to increase your ad revenue exponentially.

You see, Google Analytics can provide you with tons of valuable information. Information which can increase the productivity and effectiveness of your website. But I must say that there may be some what of a learning curve to the service. You may need to visit the Google help center or watch high quality training videos from programs like GlyticVideos. Once you've gotten a great understanding of Google Analytics, then you can fully utilize and get the most out of the service.

Using Coldfusion dedicated server, web developers can build multi-functional websites, content publishing systems, e-commerce websites, and a host of other things. Coldfusion is an easy to learn, user friendly, tag based scripting language which has connectivity to enterprise level data and strong in built searching capabilities, all of which helps in creating brilliant web pages.

Developed by JJ and Jeremy Allaire and released as an Allaire product in July 1995, Coldfusion along with Allaire was acquired by Macromedia in 2001, while Macromedia in turn was sold to Adobe Systems in 2005. A Coldfusion dedicated server is an application server used to develop both computer software and dynamic websites. Products in the same category as that of Coldfusion are Microsoft ASP.NET, JavaServer Pages or PHP. ColdFusion Markup Language (CFML) is the scripting language, similar in nature to JSP, ASP.NET, PHP and HTML is a brilliant and distinguishing feature of Coldfusion. Nonetheless it must be remembered that other CFML application servers apart from ColdFusion exist as does other compatible scripting languages like Actionscript and embedded scripts written in CFScript.

A Coldfusion dedicated server is generally used for data filled websites or intranets but remote services like SOAP web services and Flash remoting can also be generated using Coldfusion. Asynchronous forms like SMS and IMs can also be handled by Coldfusion thanks to the gateway interface, available in ColdFusion MX 7 Enterprise Edition.

Some of the value added services that come with Coldfusion are:

• generation of client-side code for form widgets and validation
• converting to PDF and FlashPaper from HTML
• database querying, regardless of platforms via ODBC or JDBC
• data retrieval from Active Directory, LDAP, POP, HTTP, FTP, Microsoft Exchange Server etc
• XML parsing, validation and querying
• client and server cache management
• clustering of server
• session, client, and application management
• Using Verity K2 for file indexing and searching
• Task scheduling
• GUI administration

Certain implementations of CFML allow enhanced functions like running in a .NET environment and image manipulation.