Comments on: Transform and split messages using an Xslt transformation pipeline component and the XmlDissasembler

By: Removing namespace from outgoing messages by .RICHARD

Removing namespace from outgoing messages by .RICHARD — Thu, 20 Dec 2007 12:38:56 +0000

[...] your development machine. I’ve written about this sample component before here were I used it another [...]

By: Mahmood

Mahmood — Fri, 17 Aug 2007 11:14:57 +0000

Hi,

i really like that example, it is quite detailed and explained properly.

nice work mate.

thanks for sharing with us.

cheers

By: Richard

Richard — Thu, 02 Aug 2007 14:00:30 +0000

@Yossi: Great idea! I didn’t think of that. That might actually work … Tell me if you try it!

I can however see cases where you’d actually like the data in the message. For example if you’d like to map it in the receive or send port (then you won’t be able to get to the data in the promoted values) but otherwise it’s a cool idea.

By: Yossi Dahan

Yossi Dahan — Thu, 02 Aug 2007 12:19:51 +0000

Hi Richard, great post, thanks.

I have another idea that might work (this is only an idea, I have not tried this (yet)) -

Could you use the xml disassembler to promote the values from the envelope to each message’s context?

If you did, you could, I believe, use the XmlAssembler on the send port to demote the properties into each sent message.

You will have to make sure the elements exist in the message (could be done in a map at the end of the receive port) and that the schema of the message is configured for property promotion correclty, but I think you’d be able to avoid loading the message to memory this way (and have any custom pipeline components (albeit SDK ones) in the pipeline.