One of the great debilitators in online business is simply the perceived (or real) lack of time. Business owners are used to moving forward. An online web presence can make them feel tied to an office chair learning skills they aren't sure they want to know.

It's not uncommon for those who deal in full time web design to have individuals contact them for a site design, but have absolutely no idea what they want. Furthermore when the designer questions them the response might be, "I don't know, just make it look nice."

Let's not forget the core values or mission of the business. Many business owners have no idea how to answer those kinds of questions. They may stare blankly for a moment or two and there's no more time for further deep thought so they go back to action - without answers.

In many cases it is possible to answer some of the questions needed, but it may require taking time away from a familiar setting. It may also require more time than you think you want to give.

If you can get to a place of concentrated contemplation you are likely to find yourself stripping ideas to their core to find out what your business is trying to accomplish and what your ultimate goals might be.

As with almost any project you can turn frustration around if you will just take the time to come to terms with your vision.

Sometimes we spend so much time 'doing' we never stop to ask the question, "Why?"

This process can be a bit like taking a bus that drives around the park. You keep looking at the flowers and the park bench and long to sit in the quiet shade of a tree and just absorb the calming atmosphere. You know they will have a positive effect on you, but for some reason you just can't seem to find the energy to get off the bus.

It seems to me there are some sites that are misguided or rarely guided that could benefit from the process of self-evaluation. These sites may look nice, but there is a sense of disconnection that may not be easy to identify, but it's fairly obvious to visitors.

Creative energy is at a minimum while business owners simply tackle what seem to be the most urgent details.

As more people gravitate to online business there needs to be a shift in the thinking of how one goes about doing business online. In many ways it can't be approached in the same way a traditional business is developed, yet that is typically the way many new web commerce ventures choose to tackle the subject.

You may discover your business will be more successful if you take some time for rigorous reflection. The time set aside can be a bit like an architect that takes the time to develop plans for a new building. You wouldn't expect the architect to simply tell a construction crew to, "Go out there and build - something."

Work at 'building' your online business in a comprehensive way. Your effort can develop a firm foundation for long-term success.

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.

Website Accessibility means the website accessible to all the users in the web including visitors with disability. Many website owners know that their website is available in the internet for visitors to access information but possibly may not know whether their website is easily accessible and even be unaware about Disability Discrimination Act (DDA).

According to Disability Discrimination Act (DDA), all the business should make their services accessible to disabled users. There is also a section in DDA which addresses that if a business offers an online service, even the information is on a single page, then the business is responsible for making an effort to make this information accessible to disabled users.

All new websites that are designed and developed should now follow the W3C (World Wide Web Consortium) and Web Content Accessibility Guidelines (WCAG) against which the accessibility of the website is measured. But when the website is found isn't complaint, then anybody can sue you legally, if they want to.

By following these guidelines, you enhance the professional look of your website, provide access to visitors who previously had not no choice, thus increasing your business prospects and finally not to forget, your business is legal.

Some basic Guidelines to increase the accessibility of the visitors

Validate HTML and CSS: To check if the HTML and CSS used is valid, W3C validator can be used. It is necessary that websites are checked as the validator automatically tells you about any errors and accessibility issues in the web pages.

Image and alternative text: For browsers which don't support images, alternative text can be used to explain what the image is about as the user will only see the text.

Resize font text: Most of the internet browsers use Internet explorer to search for information. If the size of the text can be increased by choosing the font size to the largest then it means that your website is accessible to visitors.

Use of Java script: Websites are not easily accessible when java script is disabled. Mostly people have the java script support switched off, if that's the case then make sure that you use the Java script sensibly and unnoticeably.

Check for the following,

1. Website is accessible without the use of a mouse

2. Website has a Sitemap

3. Website has link text relevant to the content (blind users use tabbing while browsing websites from one link to the other)