How to better handle big XML files that needs to be transformed after reading them in SwitchYard ?
Issue
- During the migration from
SOA-P 5
toFSW 6
users sometime face trouble to decide how they should handle big XML files that needs to be transformed after reading them throughFile Binding
inSwitchYard
. Reading and processing such huge files in memory is not a desired approach to many users. Users inSOA-P 5
used to handle this withstreaming
the files while reading them andSmooks
for 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 Binding
inSwitchYard
and 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, tools, and much more.