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.

As you know there is lots of information out there on this subject. These days we are blessed being that we have the world of information at our finger tips. This of course can be helpful but it can also be overwhelming.

If you want to generate a real income then you will need to treat your venture with a serious mind set. One that is detailed and specific. I visit a number of forums online and I notice a certain pattern.

Those who succeed seem to be far more detailed in how they succeeded. Those who fail seem to be only detailed in blaming the reasons why they failed. They do not provide specifics as to what they did.

The reason maybe because they would have to defend their actions. They would be exposed and vulnerable to criticism.

By the way this criticism would be constructive because the majority of folks out there would genuinely point out what you are doing wrong and how you can go about fixing it.

You see those who succeed are not afraid of this. They understand that they may have shortcomings and welcome constructive analysis in order to move themselves closer to their objective.

The point I want to make is this. In order to bring anything from the world of ideas into the world of reality you will need to be detailed in your execution.

I mean you could not go to a bank and ask the bank manager for venture capital if all you have is ideas with no basis in reality. You will have to be specific and provide actual actions you can take to achieve your goal.

The same should hold true before you buy into any business opportunity online or build any website. Before you invest anything you need to provide a detailed outline as to what you are prepared to do and how you are going to do it - based upon the reality of your given set of skills and circumstances.

Once you do this I promise you that you will build a real business that will generate a real income because your execution will be detailed and specific and grounded in reality.

No matter where you are in the online marketing world, you may or may not have your own website. You may wonder if creating a business website will be efficient in building your business. Here we offer you a little guidance about creating an effective online presence.

First, you should determine your website goals. Whether you are attempting to gather leads, offer knowledge, generate sales or even something different, your website design is dependant on your online marketing goals.

Once you have determined your goals, you need to know who your target viewers are and then target the photos, content and language to fit their needs and preferences. However, you should never just assume that everyone is at the same level of understanding as you are about the subject.

Then once you know who your target viewers are and their preferences, make sure that your website features ease in navigation. Just make sure that navigation is easy and simple without including a lot of distracting animated redirects.

Make sure you place a call to action on every web page of your business site, since many people simply wander the internet; they need direction of where to go and what to do once they are there. Simply capture their attention, while teaching them something new, as this will motivate them to make a purchase.

Determine whether you are trying to generate more traffic to your website, seeking sign ups or encouraging you visitors to make a purchase. On the other hand, perhaps you are trying to get people to come to a physical location. You will need some means of measuring your efforts, otherwise you will not find out what methods work and what does not work.

To allow your business to move onto the next level, you will need to follow this guidance, whether you build your own website or pay a professional to build it for you.