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

james strachan commented on CAMEL-6238:
---------------------------------------

the predicates part is a bit icky though to be honest; without predicates its 
kinda useless for many common camel use cases (as we tend to use predicates 
alot for content based routing and whatnot).

I'm wondering if instead it might be better to just make a JSONPath as a kinda 
filter/wrapper around one or more other languages, which just ensure the JSON 
gets 'beanified' first then delegates to a real expression language that 
supports expressions and predicates? e.g. I was wondering now the EL is 
standardised and has methods and property support along with predicates & 
expressions; being a standard, that might be a nice default EL for JSON; we 
just need to ensure we add a 'JSON parse' step to turn a String into Maps of 
Lists/Maps etc with jackson; then we use Juel on that?
                
> support JSONPath as a Camel Language for easy JSON filtering and expression 
> evaluation
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6238
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6238
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: james strachan
>            Assignee: james strachan
>             Fix For: 2.12.0
>
>
> JSON is a very popular message format; yet its kinda painful performing 
> expressions on it as typically you have to marshal it first into some 
> specific domain model (or Maps / Lists) and then use some general purpose 
> Java expression language on it.
> JSONPath looks pretty cool though; kinda like XPath but designed for 
> arbitrary JSON payloads
> https://code.google.com/p/json-path/
> the library is small & Apache licensed so it should be pretty easy to wrap up 
> as a Camel Language

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to