Uploaded image for project: 'Spring Integration'
  1. Spring Integration
  2. INT-2447

@beanname resolution not working for xslt-payload-transformer params

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Complete
    • Affects Version/s: 2.1 GA
    • Fix Version/s: 3.0 GA
    • Component/s: XML
    • Labels:

      Description

      The @beanname resolution that noramlly works, for example in a header-enricher expression, doesn't work for an xslt-payload-transformer expression. Looking at the source, a bean resolver is never set on the EvaluationContext for the XsltPayloadTransformer class. Whereas, the header-enricher uses a different mechanism (ExpressionEvaluatingHeaderValueMessageProcessor sets the BeanFactory on the AbstractExpressionEvaluator)

      Are there other areas where SpEL is done differently, and therefore potential for differences in operation?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mark.fisher Mark Fisher
                Reporter:
                mccarl Phil McCarley
              • Votes:
                1 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: