Using aliasses is indeed something I've already did. Also posted a long time ago about that as well: http://cxf.547215.n5.nabble.com/Problem-with-bean-properties-Map-for-searchContext-and-JPATypedQueryVisitor-td5727354.html
As a result of them I'm now creating beanpropertiesmaps dynamically (based on reflection), and store the exact property and a lowercase variation property in it. So if the property on my bean would be 'supplierCode' So then both 'supplierCode' and 'suppliercode' will work. 'supplierCOde' will still fail though. I was now thinking of recursively iterate over condition.getSearchConditions() and modify each 'property' of each statement to be lowercase. But seems like that's not possible since there are no 'set' methods available for both 'statement' and 'property'. https://cxf.apache.org/javadoc/latest/org/apache/cxf/jaxrs/ext/search/SearchCondition.html I assume recreating an entire new SearchCondition (perhaps using the builder) based on that entered the system could also be possible, but it seems a bit overkill and too complex to do. So perhaps I'll just have live with it, and try to handle both error scenarios similarly. -- View this message in context: http://cxf.547215.n5.nabble.com/FIQL-query-validation-tp5762439p5762481.html Sent from the cxf-user mailing list archive at Nabble.com.
