spring-projects / spring-projects/spring-integration
XML Aggregator [INT-571]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
David Geary opened INT-571 and commented
A simple XML aggregator that combines several XML documents into one with simple wrapper elements eg
<spring-integration-aggregated-document>
<aggregated-part>
document 1 contents
</aggregated-part>
<aggregated-part>
document 2 contents
</aggregated-part>
<aggregated-part>
document 3 contents
</aggregated-part>
<spring-integration-aggregated-document>
Example usage:
An XML message need to be transformed and forwarded to an endpoint, but as part of the transformation requires extra information from a web service call.
The XML message could be split into two copies, one copy transformed and sent to the web service endpoint, the result of this could then be recombined with the other copy (using the xml aggregator) before a final transformation (making use of all the data now available) and sent to the final endpoint
Similarly this could be used to aggregate information from multiple web service calls.
This would work with both string and node/document payloads and produce the same payload type on the output channel (assuming all input messages are of the same type)
This would also include spring integration namespace support for simple configuration.
No further details from INT-571
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue description and linked INT-571 request to clarify the intended XML aggregation behavior, payload types, and Spring Integration namespace configuration. Done should include aggregation of multiple XML messages with wrapper elements, preservation of string or node/document payload types, and simple namespace-based configuration, but the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100