How to better handle big XML files that needs to be transformed after reading them in SwitchYard ?
Issue
- During the migration from
SOA-P 5toFSW 6users sometime face trouble to decide how they should handle big XML files that needs to be transformed after reading them throughFile BindinginSwitchYard. Reading and processing such huge files in memory is not a desired approach to many users. Users inSOA-P 5used to handle this withstreamingthe files while reading them andSmooksfor transformation and it works fine. - Is there any best practice on how to implement this requirement in
FSW 6? As it is observed that while using aFile BindinginSwitchYardand letting it pass the file along to a component won’t be able to stream the file.
Environment
- Red Hat JBoss Fuse Service Works (FSW)
- 6.0.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
