Details

    • User impact:
      High
    • Similar Issues:
      MULE-4740Simplify working with Mule Registry when using a groovy expression evaluator
      MULE-3959Document the MUle Expression evaluator
      MULE-3893Improve Expression Evaluation framework to support multiple nested expressions in literal strings
      MULE-5241Add an expression editor to Mule studio.
      MULE-8440Mule expression ends with line feed throws an exception.
      MULE-5815#[Payload] is not a valid mule expression
      MULE-3143Add a Mule Context expression evaluator
      MULE-2464Improve error message for RestServiceWrapper
      MULE-3206Allow mule expressions (expression eval framework) to be used transparently in scripts
      MULE-3843Consider unifying mule expression evaluators such as header, attachments, payload, mule into a mule expression language .

      Description

      As a user I need more guidance when coding Mule Expressions.

      Acceptance Criteria:

      Have mule reduce the need to use so many expressions to code simple cases. Make Studio more friendly for typing expressions. (more code completion, more syntax highlighting, suggest properties already defined, etc.)

        Activity

        Atlassian Bamboo View RSS feed

          People

          • Assignee:
            Daniel Feist
            Reporter:
            federico.recio
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development