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.

Last February, I received a call from a man in Wisconsin asking about my writing services. He was particularly interested in having me rewrite the copy on his Web site. I was very surprised and wondering how in the heck he got my name. Then he mentioned something about my being my Internet hosting service's "customer of the month." I was very pleasantly surprised. After I spoke with him, I logged onto my email and there was an e-newsletter from my host server. And, yes, I was the "customer of the month," and my Web site was the featured site for the month.

Of course, I quickly hastened to my site and checked the traffic. I was up to over 300 visits to my home page for the morning, and the day was to end with 796 visits! I don't believe I'll ever see numbers like that again. I also received several other calls from people interested in my services.

It wasn't a complete surprise that my site was featured. Last year, I had filled out a "success story" response form on the company's site. I was later interviewed and told that I would be used as a case study. But the case study never materialized so I had forgotten about it. Thus I was very pleased when my site landed in their e-newsletter as the featured site.

My host is one of many companies where you can register domain names and get your business online. They will build a site for you; or, if you are cheap like me, you can build your own.

When I began my business a few years ago, I waited a whole year for my brother who owns an ad agency in L.A. to professionally build my Web site for free. Now he's kind of successful, and he didn't get that way by doing a lot of free work for relatives. At the time, my server was doing a lot of radio advertising claiming you could "build your Web site in 20 minutes." One day after nagging my brother once more, he became exasperated and said, "Why don't you just build your own."

So I did. I called the company and they provided templates and lots of help. I chose an animated template with a layout ideal for showcasing a portfolio. There was a bit of a learning curve. I had to play around and call for help a few times. It took me longer than 20 minutes; yet, technically, the commercial was accurate: you could really get a home page up with your contact info in 20 minutes. I believe I spent about 20 hours to get my Web site to the point where I was willing to "publish" it.

One of the advantages I have found about building your own Web site is that you don't have to rely on an outside Web Master to update it. Sometimes those fellows are swamped and it can take awhile. If I want to put a new project in my online portfolio, I can do it in a few minutes. Or if I want to add something new to my list of services, I can quickly type it in and it's done.

I found a huge difference in how I was perceived in the business community once I had a Web presence. Suddenly, I was taken seriously. These days when someone asks, "What's your Web address?" you should have it ready. And it should never be "under construction." Visitors find that very irritating. It's really not that hard to get a presentable Web site up.

As I mentioned earlier, there are numerous places where you can go to build a Web site. Just Google "do it yourself Web site" and you will get numerous options.

It is very inexpensive. My site costs me less than $100 a year for 20 pages. Some places are even cheaper. Compared to the thousands of dollars one can pay a Web designer, it's a sweet deal.

That's not to say that I don't believe in professionally designed Web sites. I still want one with more bells and whistles. I'm just waiting on my brother.

(Since initially writing this piece, my server has made the process even better. It's more professional, a lot more pages available ... and more bells and whistles.)

Last February, I received a call from a man in Wisconsin asking about my writing services. He was particularly interested in having me rewrite the copy on his Web site. I was very surprised and wondering how in the heck he got my name. Then he mentioned something about my being my Internet hosting service's "customer of the month." I was very pleasantly surprised. After I spoke with him, I logged onto my email and there was an e-newsletter from my host server. And, yes, I was the "customer of the month," and my Web site was the featured site for the month.

Of course, I quickly hastened to my site and checked the traffic. I was up to over 300 visits to my home page for the morning, and the day was to end with 796 visits! I don't believe I'll ever see numbers like that again. I also received several other calls from people interested in my services.

It wasn't a complete surprise that my site was featured. Last year, I had filled out a "success story" response form on the company's site. I was later interviewed and told that I would be used as a case study. But the case study never materialized so I had forgotten about it. Thus I was very pleased when my site landed in their e-newsletter as the featured site.

My host is one of many companies where you can register domain names and get your business online. They will build a site for you; or, if you are cheap like me, you can build your own.

When I began my business a few years ago, I waited a whole year for my brother who owns an ad agency in L.A. to professionally build my Web site for free. Now he's kind of successful, and he didn't get that way by doing a lot of free work for relatives. At the time, my server was doing a lot of radio advertising claiming you could "build your Web site in 20 minutes." One day after nagging my brother once more, he became exasperated and said, "Why don't you just build your own."

So I did. I called the company and they provided templates and lots of help. I chose an animated template with a layout ideal for showcasing a portfolio. There was a bit of a learning curve. I had to play around and call for help a few times. It took me longer than 20 minutes; yet, technically, the commercial was accurate: you could really get a home page up with your contact info in 20 minutes. I believe I spent about 20 hours to get my Web site to the point where I was willing to "publish" it.

One of the advantages I have found about building your own Web site is that you don't have to rely on an outside Web Master to update it. Sometimes those fellows are swamped and it can take awhile. If I want to put a new project in my online portfolio, I can do it in a few minutes. Or if I want to add something new to my list of services, I can quickly type it in and it's done.

I found a huge difference in how I was perceived in the business community once I had a Web presence. Suddenly, I was taken seriously. These days when someone asks, "What's your Web address?" you should have it ready. And it should never be "under construction." Visitors find that very irritating. It's really not that hard to get a presentable Web site up.

As I mentioned earlier, there are numerous places where you can go to build a Web site. Just Google "do it yourself Web site" and you will get numerous options.

It is very inexpensive. My site costs me less than $100 a year for 20 pages. Some places are even cheaper. Compared to the thousands of dollars one can pay a Web designer, it's a sweet deal.

That's not to say that I don't believe in professionally designed Web sites. I still want one with more bells and whistles. I'm just waiting on my brother.

(Since initially writing this piece, my server has made the process even better. It's more professional, a lot more pages available ... and more bells and whistles.)