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.

The greatest breakthrough of the Web 2.0 age is the advances made in web page coding. Previously, an interactive web page would require you to click on the control to trigger the action, then the request would be sent to the web pages server, and you were stuck waiting for the page to reload. This is an inconvenience on your part, as you are stuck waiting. Similarly, if you are the owner of the webpage, it is an inconvenience to your users to have to wait. Furthermore, if you are offering your services or products, you are losing potential customers and gaining downtime on your webpage.

But AJAX, which stands for Asynchronous JavaScript and XML, is a new type of web coding technology which allows you to create an interactive website that does not need to reload and communicate with the server every time an action is taken. For you as a web page owner, this means faster loading times for your customers, as well as more interaction with the page on the end users' side.

AJAX uses a combination of Java, XML, HTML, and CSS coding, all rolled into one to create a unique and interactive web pages.

Are you wondering where AJAX has been employed on the Web? Ever used Google Maps? Google Maps allows you to drag the map, zoom in and out, as well as set markers on the map without the need to bee constantly interacting with Google's server.

If you want to create a unique and interactive webpage with less loading time, allowing your members to view more in less time, AJAX coding is the way to go.

So you managed to get a website up and working. You managed to set up a pay per click campaign. But you have not managed to get lots of buyers, callers, joiners, clickers or whatever it is you were after. You may even be advertising to a niche market, yet your website speaks to a general audience. If you try to be everything to every body these days and you will end up being nothing to anybody. So let's look at how you might make changes to your site to speak to a niche and get some conversions.

News Flash. The general store can't compete with the amazons of the world.

If you try all by yourself to compete with mega mart, you will get lost in the big black wormhole of the internet-- also known as the limp, lame, solitary server for misplaced website owners. That's why you choose a segment or a niche strategy. It offers you an opportunity to carve a market share out of that big giant pie. The trick is to identify the niche market or brand audience who will value the service or product enough to pay for it.

How can you position to a primary target audience ?

Don't shoot at the ocean hoping to hit a fish. You need to follow a plan or niche strategy to develop your website so it speaks to this primary target audience. A website is a marketing tool. So here is a brief outline regarding how you might go about the process of creating a well-positioned, marketing savvy website that is not generic. This is an extremely simplified website plan for positioning to a target audience but it outlines a process that you can follow.

• Define your site- Before you can actually choose the type of software or tool you will need to create your site, you need to first determine what KIND of site you want. Is it a site to promote your business? Or an eCommerce site to sell stuff? Is it a community forum for like minded. You site definition determines which development tools you'll need. A free template might do the trick or you might like to look into ecommerce programs.

• Define your goals- What do you want this website to do for you? Sell? Get additional business? Advertise more high-profit items or services? Serve as a status gateway for your sales and marketing team? Do you want it to be an informational platform that is supported by advertising. Writing down your goals gives you a focus.

• Define your target market- It's not "everyone on the internet". Big companies spend MILLIONS to define their market and create an appropriate strategy. So you need to research the segment of the population who you are trying to reach. If it's teenagers, is it female teens with self esteem issues? Is it teens who are book worms? If you know which segment it is, you can further define the audience and know how to speak to them.

• Define features- These are the features you want on your site. If you are a real estate firm, do you want an amortization calculator? Do you want a venue for people to leave comments? Do you want a slide show, streaming video, audio files? Do you want a schedule of how-to clinics and sign up capability for these clinics? What about registration and payment capability? All of this helps determine the tools you use, the package you might buy the host you will choose. Some hosts are better if you happen to be posting lots of video or audio content for example. Still others offer ecoommerce packages with a higher level of tech support for these customers.

• Target marketing strategy-Your marketing strategy is a plan to reach specific objectives. It does not have to be catchy. It just has to define what you would like the site to accomplish. Example: For instance, you want your computer repair business to cater to home office entrepreneurs who want same-day repair. Your focus is getting computers fixed fast from a remote location and keeping the business person at peak productivity by minimizing downtime. You may also want to get an affiliate cut for spyware you recommend on your website and other products that keep computers virus free and performing smoothly. You want to keep in touch with your market through a newsletter with free tips on how to boost performance and with latest virus alerts. You would like to start offering monthly contracts for being the "IT Department" for the home office entrepreneur and eventually establish yourself as the go-to company for IT services.

Remember to write or use copy that does not focus on yourself or your company, but think strategically in terms of how your product(s), service or company benefits your target market. Then your website should guide them along the path to the action you wish them to take much like a live sales person would do. Plan your website well and it could become one of your least expensive and highest yielding marketing and sales tools.