Re: How to solve the multiple schema definiton case?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Curt,

This is a good teqnique, but to the question of being preferred, can I
ask a followup question? When you algorithmically create this
namespace, are you adding to the message context, or to the message
instance itself?

The reason I ask is this, to my mind (at least until now) a source xml
message received from a third party should be immutable and match the
definition provided by the vendor when it hits the messagebox. If your
approach leaves the source message untouched, I am all over it. If
your approach alters the inbound message in some way, I need more
convincing. Help me out here :-)

Thanks
Chuck

On Jan 24, 8:30 am, "BTSWizard [MVP]" <curt.peter...@xxxxxxxxxxxx>
wrote:
Emre,

This is actually a very common situation, and as you have identified
there is usually something in the document that can be used to
determine uniqueness. I use a custom pipeline component that allows
you to specify an algorithm that you can use to generate a namespace
for the document. You specify a base namespace, then one or more XPath
expressions to values in the document that you want to append to the
base namespace. This is the preferred approach, once this is done,
BizTalk can then treat this document as a fully typed document. The
pipeline component is put in the decode stage of the pipeline.

If you'd like a copy of the source for the component email me direct.

Cheers,

-Curt

.

Relevant Pages

  • System.Random Algorithm
    ... What´s the algorithm that the .NET System.Random namespace uses? ... Ticks, TickCount, or something else. ...
    (microsoft.public.dotnet.framework)
  • Re: How to test sound freq?
    ... I have made tone generator, using DSound buffers and simply cos ... You say that I can detect tone frequency with that algorithm? ...
    (comp.dsp)
  • Pipeline Context properties
    ... I have a custom pipeline component. ... I need to access the filename the send port is going ... Thinking that perhaps the namespace was "wrong" for 2006, ... string curName, curNamespace; ...
    (microsoft.public.biztalk.general)