[ https://issues.apache.org/jira/browse/CXF-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130207#comment-14130207 ]
Sergey Beryozkin commented on CXF-5990: --------------------------------------- Having the ability to set a custom parser property is useful on its own, so I applied the patch, thanks. I'm not sure how to generalize the processing of numbers like "1*" because it is not ">= 10" but rather "all numbers starting from 1", etc. May be something like that: - replace all '*' with '0' and inject an integer value, so in case of "1*" we'd have '10' injected. - PrimitiveSearchCondition should have a PrimitiveStatement with the original "1*" value. - update JPA visitor as needed, say if we have an integer and 'equals' op but the original property value has '*' then it can be acted upon... Not sure if it makes sense, if it does then please consider doing another patch Thanks, Sergey > Integration custom parser > ------------------------- > > Key: CXF-5990 > URL: https://issues.apache.org/jira/browse/CXF-5990 > Project: CXF > Issue Type: Improvement > Components: JAX-RS > Affects Versions: 3.0.1 > Reporter: Romain Castan > Labels: features > Fix For: 3.0.2, 3.1.0 > > Attachments: patch1.diff > > > Hi, > I would like to use a custom parser with the same parameters of FiqlParser. > With the property "search.parser" is not possible to reuse the following > parameters "props" and "beanProps". > To continue on my project, I modified the code of SearchContextImpl (see > patch1.diff). But perhaps, there is already a solution for my demand. > Could you give me the best solution? > I wanted create a new parser because today with FiqlParser, it's not possible > to apply a filter on integer attribute with '*' value. > I don't know if this feature has been forgotten? -- This message was sent by Atlassian JIRA (v6.3.4#6332)