Problem with partialTriggers in ADF Faces

Question

I´m using JDeveloper/Oracle Appserver 10.1.3.
Here is what I find strange:
I wish to display an error message next to a textfield using the autoSubmit/partialTriggers functionality.
<afh:cellFormat>
<h:panelGroup>
<span title="#{textBean.translatedTexts['popup_338']}">
<h:outputText value="#{textBean.translatedTexts['datum__direct_payment.jsp_2516']}" />*
</span>
<af:inputText simple="true" id="paidDate" value="#{directPaymentBean.directPaymentFormBean.paidDate}" maximumLength="10" inlineStyle="width:120px" autoSubmit="true" styleClass="input" valueChangeListener="#{directPaymentBean.doIt}">
<fpw:convertDate
messageKey="ange_datum_i_ratt_format__direct_payment.jsp_2422"
datePattern="#{framework.fpwUser.longDateFormat}"/>
</af:inputText>
<af:panelGroup partialTriggers="directPaymentForm.paidDate">
<af:message for="paidDate"/>
</af:panelGroup>
</h:panelGroup>
</afh:cellFormat>
The request is submitted and the Converter fails but the message is not displayed. However if I change the af:message ti af:messages it works. It also works (with af:message) when I do a full submit with a command button. Both scenarios above indicate that:
1. The trigger fires, at least for af:messages meaning that the syntax is OK
2. The message is stored with the right id (paidDate) bacause the message gets display at full page submit.
It it something funny with af:mesaage and partialRendering?

Answer 1

Hi,
Ok that's a lot of different issues, I'll start with the last one.
I thought that only the values (text fileds) that has declared partial triggers were supposed to be sent in the request but all data is actually sent at a PPr-request. I can live with it though. Just wondering.
It depends if you're using 10g or 11g and also the type of events. Most of the times, everything will be sent though, but not everything is going to be processed in case of 11g
But, when I tell the panel group containing the message to listen to both text fields funny things happen
Ok, that's strange. Let try a programmatic approach just to see what happen. Try the following in your page.
<af:inputText id="paidDate" value="something" ...>
  <f:valueChangeListener binding="#{messageController['paidDate']}"/>
</af:intputText>
<af:message for="paidDate" binding="#{messageController['paidDate'].component}"/>Then create a request scoped managed bean named messageController wiith the following class:
public class MessageController extends HashMap<String, MessageController.Refresher>
    public Refresher get(String id)
        Refresher refresher = super.get(id);
        if (refresher == null)
            refresher = new Refresher();
            super.put(id, refresher);
        return refresher;
    public static class Refresher implements Serializable, ValueChangeListener
        private UIComponent component;
        private Refresher()
        public void processValueChange(ValueChangeEvent ev)
            RequestContext.getCurrentInstance().addPartialTarget(component);
        public UIComponent getComponent()
            return component;
        public void setComponent(UIComponent component)
            this.component = component;
}That code will refresh the bound component (the message) whenever the value in the component using the listener (the inputText) changes. In your case it might do the trick.
Regards,
~ Simon