change target name space in receive pipeline

Question

0.00/5 (No votes)

See more:

Hello all,
I want to Add/change the Target name space of a incomming message (JSON schema) in receive pipeline dynamically.

Can some one help me on this ? How can i design receive pipeline?

Note: Incoming Messages are json Format.

In simple words what i want is :

There will be different json schema files(incoming json schema) will open that schema in receive pipeline and will add/or Chnage the Targetname Space in it and will send to Send port ( this is my sample POC).

Note: we are sending request to /BTSHTTPReceive.dll through ajax request.

Thanks
Pavan.D

Posted 19-May-15 19:41pm

Member 10729318

Add a Solution

Comments

Abhipal Singh 20-May-15 4:40am

The default receive pipeline components in BizTalk will not be able to help you change the target namespace.

You need to develop a custom pipeline component which will do the job of
1) Converting JSON to XML
2) Changing target namespace.

All you need to do is write a custom Decode component and call JsonConvert.DeserializeXmlNode() to convert JSON to XML and then you can change the target namespace of XML document.

However, if you explain what you are trying to implement a bit more, then may be we can provide a more elegant solution.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)