Hi,
I just think something like your solution, but in my opinion a better
solution coul be
to extends the EIP Abstract Splitter and ovveride the createParts
methods so:
- if you've "n" attachments
- it will create 1 + n exchange where the first message is the soap body
and the other n messages
are n small messages one for each attaments where the "message
content" could be a simply xml
describing the attachment.
In this way after doing that you can put a splitter to elaborate the
attachments in parallel way.
Do you agree on that???
Andrea Zoppello
netflexity ha scritto:
I created a LW Component that would create the following XML out of SOAP with
attachments:
<Extractor>
<Response>
Response message itself
</Response>
<Attachments>
<Attachment>
Base64 or plain attachment
</Attachment>
......
Andrea Zoppello-2 wrote:
Hi all,
I'm trying to use a process that has a HTTP SOAP Binding component as
consumer.
I've just verified that if i call the process with a SAAJ client the
attachment are copied
in the attachment part of the normalized message.
My problem is that i want to handle separately the attachments and the
soap body part
of the message.
I need a component that "splits" the attachments and message content of
the normalized message.
Any idea on that??
Andrea Zoppello
