As a user I want single expression language that I can use in instead of long list of expression evaluators for both evaluation and enrichment

is duplicated by

MULE-5912 As a user I want a default (script based) expression evaluator that I can use directly anywhere where Mule expressions can be used.

1.	Define ExpressionLanguage interface	Closed	Daniel Feist
2.	Implement MVEL ExpressionLanguage	Closed	Daniel Feist
3.	Define and implement context objects for server, mule and app	Closed	Daniel Feist
4.	Allow for the use of expression language via ExpressionManager	Closed	Daniel Feist
5.	Define and implement dynamic message expression language context (uses message currently being processed)	Closed	Daniel Feist
6.	Provide a Flow context with property "name" if event is available	Closed	Daniel Feist
7.	Provide a process() function if event is available	Closed	Daniel Feist
8.	Define and implement ExpressionLanguage extension mechanism	Closed	Daniel Feist
9.	Implement an xpath() function to perform xpath evaluation within Mule expression language	Closed	Daniel Feist
10.	Support the use of Mule Expression Language for enrichment	Closed	Daniel Feist
11.	Provide a simple XML element that can be used for executing an expression within a flow	Closed	Daniel Feist
12.	Add tests methods using expression language for ExpressionTransformer/ExpressionFilter etc.	Closed	Daniel Feist
13.	Allow configuration of expression language functions and alias in xml configuration file	Closed	Daniel Feist
14.	Provide a regex() function that can be used instead of RegexExpressionEvaluator	Closed	Daniel Feist

There are no comments yet on this issue.

Vote (0)

Watch (0)