Recently I had an issue while using the af:message component for the inline faces messages on the UI instead of the default message popup.
The normal use of this af:message component is to drop it next to the inputtext or any input component for which you need the inline faces message and set the for property to input component id.
For me this input text was inside an iterator and it's not working in the conventional way.
Let me take up an example and show you.
Usual way :
1. The structure of the jspx page is like below.
3. The properties for the 1st af:message component is as below.
4. The properties for the 2nd af:message component is similar to first.
I was expecting all to work properly as there was nothing seemed wrong on the first look.Let's c what happened.
Oh no ! Only the input text outside the iterator seems to be giving the desired result.
Fix:
1. Instead of it2 as the for property in the second af:message, we need to give it as #{vs.index}:it2 where vs is the varstatus property of the af:iterator.
Ignore the jdeveloper error on the for property.
Now, let's c how it works.
BAM! All inputtext's work as expected.
Why this works this way:
When a component is inside an iterator or a table, the html ids are like 0:it2, 1:it2 ... etc as all of them need to be unique. So, by appending #{vs.index} we are able to append that 0 or 1 to the actual id of the component.
As u can see the ids are i1:0:it2, i1:1:it2 and i1:2:it2, i1 is directly appended by adf as iterator is the parent component and i1 is the id of the iterator.
PS: This issue is no more there in Jdeveloper 12c. So, the usual way works fine and there is no need of this work around.
Cheers ! Keep Learning ! :)
