Max Katz

There are four components in the a4j: tag library which enable you to send an Ajax request. They are a4j:commandButton, a4j:commandLink, a4j:support, and a4j:poll. All provide rather specific functionality. For example, a4j:commandButton will generate an HTML button that fires an Ajax request. a4j:commandLink will do the same but generates a link. a4j:support is always attached to another JSF component to enable sending an Ajax request based on some event supported by the parent component. a4j:poll which allows sending Ajax requests periodically. There is one more tag called a4j:jsFunction. This tags gives you a lot of power and flexibility. a4j:jsFunction lets you send an Ajax request from any user-defined JavaScript function. It can be a custom function or from any component-event as well. The good news is that it works just like any other tags I listed above, it has all the same attributes such as reRender, action, actionListener, bypassUpdates, ajaxSingle and so on.

Suppose you would like to send an Ajax request when the mouse moves over some plain HTML content on the page, in other words, when mouseover event occurs. We can’t use a4j:support because it can only be attached to another JSF component. One option is to write a custom JavaScript function that would fire an Ajax request, include any parameters from the page and of course participate in JSF life cycle. It’s probably not something we want to, right? We don’t do it with a4j:commandButton, so why would be suddenly write such JavaScript function? Well, as it turns out we don’t need to do it because a4j:jsFunction provides exactly what we need.

When we place a4j:jsFunction on a page, a JavaScript function will be rendered that fires a regular Ajax request, not much different than we use a4j:commandButton or a4j:support tags. All we need to do is just call this function.

   

     

          
Espresso
          
Cappuccino
          
Tea
     
  
   
     
     
   
   

In above code we call what appears to be a regular JavaScript function named setdrink(..). In fact it is a regular JavaScript function. It’s defined via a4j:jsFunction tag. This is what the tag rendered on the page:

//

Notice that setdrink(..) takes two parameters. These parameters are passed to the server using a4j:actionparam tag. The name in a4j:actionparam is not important but should be set to something. The order is important. In other wordds, the value of the first parameters to the JavaScript function will be set into #{drink.bean} property in backing bean. Finally reRender attribute is used in the same way as with any other tag.

The managed bean looks like this:

public class Bean {
   private String drink;
   private String bgColor;
   // getters and setters
}

Here is one more example:

Nothing is stopping us from doing something like this:

function sendAjaxForm(){
   // custom code here
   fireAjax();
}


   
   
   
   

If there was an action you wanted to invoke, then a4j:jsFunction would look like this:

Let’s look at another example.

In above example, when the list changes an Ajax request is fired and rich:dataList component is updated to show the new list. This is just an example to illustrate how a4j:jsFunction works. I’m guessing that most developers would just nest a4j:support tag to achieve the same result:

If you were not sure how a4j:jsFunction tag works, I hope this posts makes it all clear. The tag is actually very simple, it works just like all other tags that fire an Ajax request but also provides a lot of flexibility. It’ s now possible to fire an Ajax request from any custom JavaScript function or client event without having to write a single line of JavaScr