The requirement is to add couple of fields on a OAF page. Here is what I did:
- Created custom VO by extending the standard VO
- Added fields to the page via personalization.
The issue is that the values for the custom fields on the page were not showing up. On investigation, I found the VORowImpl getter getAttrInvokeAccessor was not being called for my custom attribute. I tried to check the difference between the attributes for which the getter was called and for which it was not called. I couldn't find any and I'm totally left clueless as to what determines the getter to be called.
Really appreciate your help to move ahead.
Edited by: AnilMenta on Mar 5, 2013 10:40 AM
First of all, Could you please make sure that Extended VO is being picked up during the execution of the page . Ensure that extended VO is substituted
If the VO is substituted then try Steps below
1. Enable the diagnostics .. show log on page statements
2. Search for your custom VO name .
If you can find your extended VO here, then substitution is right and page is picking up the extended VO.
I verified that my extended VO is picked up by the page. I also saw in "About page" and it does show my extended VO over there. Also, I'm referring to custom attribute for the custom field on the personalized page. So the page would have errored if the substitution did not work as the attribute would not have been recognized.
Unless the attribute is not being used in any of the UI or any of the other calls,
the getter will not be called,
make sure you have got the attribute used to get your custom attribute getter called.
You mentioned that you started using it in the personalization, is still the issue persists?
The issue is resolved.
custom getters were not called because my personalization where I was using my custom attributes was not in place. Once I put my personalization with custom attributes back, my custom getters are called now.