a4j:support immediate JSP

# Behavior of the "immediate" attribute is changed

## Description

Since we've migrated to the JSF 1.2 standard in RichFaces 3.2.0 the "immediate" attribute works exactly like it should according to the JSF 1.2 specification: the default ActionListener stops execution after the Apply Request Values phase, so there is no interaction with a model any more. We could not use the standard JSF API before as soon as we had to support not only JSF 1.2, but JSF 1.1 as well. We used our own hack that emulated the behavior of the attribute. This approach had a side effect that allowed interacting with a model but now this side effect is gone.

## Links

- RichFaces Forum

## How to reproduce

    ...
    <h:form>
    	<h:inputText id="oneA" value="#{bean.name}" size="8">
    		<a4j:support event="onkeyup" reRender="three" immediate="true" focus="oneA" action="#{bean.actionOne}"/>
    	</h:inputText>
    	<h:selectBooleanCheckbox id="twoA" value="#{bean.option}">
    		<a4j:support event="onclick" reRender="three" immediate="true" focus="twoA" action="#{bean.actionOne}"/>
    	</h:selectBooleanCheckbox>
    	<h:commandButton id="go" value="Submit"/>
    </h:form>
    <h:outputText id="three" value="#{bean.name} #{bean.option}"/>
    ...

## Causes

Behavior of the "immediate" attribute is changed according to to JSF 1.2 specification.

## Workarounds

The solution includes the following steps:

- replace "immediate" attribute with `ajaxSingle="true"`

- add "process" attribute. This attribute points to the components that should be processed together with the command component.