Jim Murphy wrote:
>I don't get why this is a problem. Say I have a handler that wants to
>transform a request in some way (decrypt, remove a Header whatever).
>Isn't that just consuming one stream and producing another? If it wants
>to consume one stream map that to Java using some marshaling/binding
>mechanism to operate on then generate the result stream based on that
>why would it matter?
>Why wouldn't a very thin Axis working with several Java
>binding/marshaling layers be a compelling approach?
Problem is, I have yet to see a SOAP stack that works this way. "Consuming
one stream and producing another" implies that each intermediary node would
potentially have to go from XML->Java->XML before the call got passed to
another the next intermediary node. This would certainly allow each node to
use it's own data binding schema - but think of the serialization
performance hits!
-Jon
