camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raúl Kripalani (JIRA) <>
Subject [jira] [Resolved] (CAMEL-9097) XSLT Aggregation Strategy
Date Mon, 14 Sep 2015 00:03:46 GMT


Raúl Kripalani resolved CAMEL-9097.
    Resolution: Fixed

Hey Ranil,

Thanks a lot for your contribution! I applied it on commit cc71df3100fa47e9c757a1213589e06dddd4a856.

I made a few changes:
* allow the user to set the property in which the new incoming message will be injected via
a setter; remove the header for this as in practice the XSLT param name is fixed, so it's
OK to specify it at development time.
* added fluent builders.
* added this aggr. strategy to the {{AggregationStrategies}} toobox.
* changed the default property name to {{new-exchange}} to comply with typical XSLT naming
* explicitly specified the Saxon processor in the tests, as Xalan doesn't handle node-set
parameters well


> XSLT Aggregation Strategy
> -------------------------
>                 Key: CAMEL-9097
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Ranil Wijeyratne
>            Priority: Minor
>              Labels: aggregate, xslt
>             Fix For: 2.16.0
> It would be great to have an built in aggregation strategy that allows to use an xsl
stylesheet to aggregate messages.

This message was sent by Atlassian JIRA

View raw message