By Juergenkress-Oracle on Feb 12, 2015
had a post about the solution to suppress ADF LOV Like operator and
prevent LOV popup loading when user is typing existing value - Suppressing ADF LOV Like Operator Filtering.
Thanks to a blog reader, there was one use case found, when Like
operator was not suppressed properly. This is fixed now and I would like
to post updated sample application here.
Additional method is overridden in LOV VO implementation class - applyViewCriteria(ViewCriteria, boolean). Besides previously overridden method buildViewCriteriaClauses(ViewCriteria), this method provides additional handling for LOV Like operator suppression. Download sample application - ADFTableApp_v2.zip.
Blog reader reported an issue, when LOV value was changed to 10, again changed to 100 and again 10, then LOV popup was opened on the last change. This should not happen, as value 10 exists in the LOV. It seems like when LOV value is changed to the same as it was set before, ADF BC executes extra call for LOV filter through applyViewCriteria method. This is why this method is overridden as well as buildViewCriteriaClauses.
Both methods are overridden and check for STARTSWITH (Like) operator is implemented:
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.