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.

That should be the main reason that you create a website so that it will work for you in your chosen endeavor. When you build a website it is important to understand what makes a website work.

Firstly when you go online in the research mode you type in a keyword relative to your question. Then a number of sites come up with content relative to that keyword. Then you visit a site and see if it contains the answers you seek.

The best sites are highly relevant to your search and provide content that addresses your needs. This content is laid out in a way that makes sense. Navigation is straight forward and there are few distractions. As a result you get the answers you seek and because it is presented logically in a way you can understand you relate to it and as a result you follow its recommendations.

This is exactly the way you want to build your website. Good content is king but not only that - content that is relevant and solution orientated rather that sales orientated will deliver better results. This way you become your visitor's friend and we all listen to our friends.

When people can understand and see results credibility develops. Then share a few secrets here and there and you will have a friend for life.

Get this right and you will build a website that will work for all parties concerned. This may sound a little complicated but it actually is not. We are all human beings and we have far more things in common than not. So observe how you use the internet and what your expectations are then you will understand what others expect.

To learn how to put all this together select any of the following links.

Did you know that your css code could be slowing down your website? Did you also know that there is a free solution out there that can help you optimize or reformat your css code for speed and readability? This article is going to explain the benefits of optimizing your css code and the reasons why all web designers should be doing it. First we need to take into account the 2 reasons why you would want to reformat your css: readability and optimization.

Readability

Having nicely formatted css that easily readable is very helpful when you are developing a site. Most of us (me included) can get pretty sloppy when in a hurry to develop code, and a formatter can really help out to make it more readable.

On development teams where both Macs and PCs are used, sometimes line breaks are not read correctly across platforms and your css can end up all on one line. A formatter can help get your code looking pretty again.

Optimization

The opposite of readability is optimization. One problem with CSS is that it can get pretty file-size heavy when designing with it - especially on complex layouts. Optimizing your CSS will strip out all unnecessary characters and leave your CSS lean and mean.

Optimizing css is great to do once you've finished your site and don't plan to work on the design very much anymore.

The css formatter is a great tool because it can do both! You can format for readability while you are designing, optimize when you go live, and reformat it for readability if you ever need to work on it again. It's really a 'win win' thing to do.