cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Castan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5990) Integration custom parser
Date Thu, 11 Sep 2014 13:12:33 GMT

    [ https://issues.apache.org/jira/browse/CXF-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129997#comment-14129997
] 

Romain Castan commented on CXF-5990:
------------------------------------

Hi,
If we have a number like '1*', It can't to be converted to '10' because this number can have
a lot of values as:
* 1
* 10
* 11
* 12
* ...
* 100
* 1000009

Another example, if we have a number like '2*2', the different values are:
* 202
* 212
* 222
* 232
* ...

I already implemented my custom parser to take into account this feature for my project, but
my parser use the same parameters than FiqlParser. Currently, I think It's not possible to
inject these parameters with Spring for a custom parser.
I updated the code of SearchContextImpl to integrate a new custom parser (see attach file
patch1.diff). I know that this patch it's not applicable but I have able to test my custom
parser.
Do you have a better idea?



> 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
>         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)

Mime
View raw message