Hello,
I have one question about the architecture of servicemix. It's about the
strategy servicemix uses for processing of xml.
We are trying to find some platform that will replace cocoon2 as our xml
routing system, and servicemix seems to be nice thing for our needs.
However, I noticed that there is one thing which is not really nice. The
most (actually all I have seen) components are using dom processing. Dom
is nice to work with, but this makes things quite bad in the performance
point of view. Working with dom is expensive, and for example Cocoon
moved in version 2 from dom to sax. Our messages will have size of
megabytes, so Dom is not an option for us...
What I want to know is whether there is an effort to move servicemix
somehow to sax processing, or being smart about message Source objects
in processing. Generally how is it with these things.
thanks for any comments,
Martin
