Is it possible to configure an NServiceBus endpoint (on Azure transport) to accept a simple string as input? -


we have nservicebus endpoint monitors azure service bus queue (using azure transport). not clients send messages queue .net-based.

can nservicebus endpoint configured accept simple string input?

i've tried intercepting messages class implements imutateincomingmessages, @ point deserialization azure transport has failed.

i can inspect message coming in in class implementing imutateincomingtransportmessages, i'm not sure if right place.

what best way configure nservicebus handle message being published in following format (keep in mind can come via java or node sdks, or via azure rest endpoint):

 var brokered = new brokeredmessage("this plain string represents data.");  queueclient.send(brokered); 

deserialization of message fail, because contains string, not byte array expected azure transport deserializer.

ps: know possible expose endpoint wcf service, have nservicebus.host processes pull queue , wcf solution not feel right solution me.

as mentioned on twitter earlier, including here completeness...

if want integrate natively, have modify parts of nsb pipeline accomodate environment.

see https://github.com/yvesgoeleven/nservicebus.asbnativeintegration example of such integration.


Comments

Popular posts from this blog

javascript - gulp-nodemon - nodejs restart after file change - Error: listen EADDRINUSE events.js:85 -

Fatal Python error: Py_Initialize: unable to load the file system codec. ImportError: No module named 'encodings' -

javascript - oscilloscope of speaker input stops rendering after a few seconds -