So, I think it is an umbrella issue and I agree to have a set of components similar to SI-XPath components.
In additional it may be interestingly to introduce two new transformers:
But it is exactly out of scope of this issue...
I'm not sure which implementation of JSONPath should we use or we should implement our own...
How about this one: https://github.com/beckchr/staxon/wiki ?
Regarding JSONPath ability inside the SpEL: we can achieve it via StandardEvaluationContext#registerFunction(), so in the end it will look like this:
When we will register some static method from potential JsonPathFactory on each EvaluationContext creating.
But then we should move this new module to the Spring Integration project.
And as I see we may do the same for XPath right now.
But it isn't trivial now: there are a lot of direct EvaluationContext creating bypassing ExpressionUtils...
And also maybe it is in the scope of the task: https://jira.springsource.org/browse/INT-1639