[jira] Resolved: (CAMEL-1024) [IDEA] could we refactor the expression implementations (invoking JavaScript / Groovy / Ruby / XPath / XQuery et al) so they are easy to invoke from any library - not just from an Exchange?

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-1024.
--------------------------------

    Resolution: Won't Fix

We had an API overhaul for 2.0. Lets keep it as is now.

> [IDEA] could we refactor the expression implementations (invoking JavaScript / Groovy / Ruby / XPath / XQuery et al) so they are easy to invoke from any library - not just from an Exchange?
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1024
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1024
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: James Strachan
>             Fix For: Future
>
>
> mostly they are about setting key/value pairs and firing the expression off. I wonder if we could refactor the implementations of the languages so we mostly have a common bit of code that binds the state (exchange / headers / properties / body etc) and have a non-camel-exchange specific API so we could invoke the expressions from other libraries?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.