cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-5990) Integration custom parser
Date Fri, 05 Sep 2014 15:25:29 GMT


Sergey Beryozkin commented on CXF-5990:

Sure, registering a custom parser class can be simpler compared to registering an instance,
though one can use a constructor injection from Spring/Blueprint if needed.
Perhaps another option is to register a JAXRS 2.0 ParamConverterProvider for Integer - that
should be much simper than writing a custom parser.
Re your example, if we have a number like '1*', is it expected to be converted to '10' ?

Cheers, Sergey 

> Integration custom parser
> -------------------------
>                 Key: CXF-5990
>                 URL:
>             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

View raw message