Add support for SB-Messaging adapter (empty message body rather than null)

[jcools85]

I'm using ServiceBus.AttachmentPlugin in a hybrid integration solution, and my consumer (in this case BizTalk's SB-Messaging adapter) doesn't like the ServiceBus message body being null.
I can replace the message body stream in the receive pipeline to let my flow work, but the SB-Messaging adapter still logs an error in the eventlog:

The Messaging Engine received an error from transport adapter “SB-Messaging” when notifying the adapter with the BatchComplete event. Reason “Object reference not set to an instance of an object.”.

Proposed solution:
Add an option to the AzureStorageAttachmentConfiguration constructor to avoid an empty message body when sending a message. For example, the blob.Name that is written to the custom property could also be written to the ServiceBus Message Body.

[SeanFeldman]

@jcools85 would an empty byte array work for your scenario?

[jcools85]

@SeanFeldman yes, just tested with an empty byte array and that seems to work.

[SeanFeldman]

@jcools85 have a look at the change here. This would need to be an opt-in configuration. Would that work for your scenario?

[SeanFeldman]

Also, would it be correct to say that this issue adds support for "BizTalk's Service Bus Messaging adapter"?

[jcools85]

Looks good! That would indeed work for my scenario.
And yes, you could say this adds support for the SB-Messaging adapter, because besides this little issue it works perfectly. You do however have to build the "receive" logic in BizTalk. But a simple pipeline component that replaces the body stream with a new stream from blobstorage does the trick.

[SeanFeldman]

Looks good! That would indeed work for my scenario.

Great. I'll release that over the weekend.

And yes, you could say this adds support for the SB-Messaging adapter, because besides this little issue it works perfectly.

Great. I love to see CodeIt leveraging this plugin for various solutions.

You do however have to build the "receive" logic in BizTalk. But a simple pipeline component that replaces the body stream with a new stream from blobstorage does the trick.

That's likely due to the fact that the receiving part of the SB-Messaging adapter assumes the body is always there. Which is OK as long as the BT pipeline allows you to have the step before to consolidate the payload and the message.

[jcools85]

Great. I love to see CodeIt leveraging this plugin for various solutions.

Thanks for handling this request so swiftly @SeanFeldman !
Will be used in production at one of our customers before summer :)

[SeanFeldman]

@jcools85 do you mind to share your Twitter account (for credits)?

[jcools85]

@jcools85 do you mind to share your Twitter account (for credits)?

Sure! my twitter handle is @jcools85 as well. I just followed you, was surprised to see I wasn't following you there already, because you do pop up on my feed a lot :D

[SeanFeldman]

Found an issue with the body replacer. Will release once the other PR for the milestone is closed.