RE: Wrong Message Type applied to message instances
- From: vrouet <vrouet@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 Nov 2005 03:18:06 -0800
Stephen,
Sorry I did not take the time to thank you for your reply. I've tried what
you suggested but we are still stuck with the same problem. In fact we are
considering writing our own pipeline.
Thanks again
vrouet
"Stephen W. Thomas" wrote:
> Hello.
>
> I have seen a problem like this in the past with my messages getting the
> wrong message type.
>
> Are you specifying the schema in the Collection List inside the
> Disassembler? If so, I think that’s causing the problem. Make sure the
> schemas are in a different assembly then the pipeline.
>
> In my case, I fixed it by separating out the files into different Receive
> Location under different ports. But you might not have that option.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
> http://geekswithblogs.net/sthomas/
>
>
> "vrouet" wrote:
>
> > Hi,
> > Has anyone ever tried to process a schema with mixed elements as below?
> > Sometimes the file can contain only <invoice> or only <service> or both.
> >
> > <Root xmlns="TN.MyEnvelop">
> > <Invoice xmlns="TN.MyInvoice"/>
> > <Invoice xmlns="TN.MyInvoice"/>
> > <service xmlns="TN.MyService"/>
> > </Root>
> >
> > We have deployed 3 schemas, one for the envelop and one per element type
> >
> > Through a pipeline, the envelop does the job of splitting the records but
> > the instances are saved to the message box with the same MessageType! The odd
> > thing is that the MessageType used is the one of the last element found. In
> > the example above the MessageType given to the messages would be
> > "TN.MyService". We tried to end the file with a <Invoice> element and the
> > allocated MessageType becomes "TN.MyInvoice"!!!
> >
> > A test with the xmlDasm utility gives an output that is correct, each
> > message is recognized with the proper MessageType.
> >
> > Against the orchestration process, I ran SQL profiler and watched the "exec
> > [dbo].[bts_InsertProperty]" procedure of the BizTalkMsgBoxDB. The problem
> > seems to come at this stage when the message is inserted in the message box.
> > All are inserted with the same MessageType.
> >
> > This causes wrongly types messages in the MsgBox i.e. not exploitable.
> >
> > If anyone can give me a clue or share a past experience. Am I missing the
> > obvious? Many thanks
> >
> > vrouet
> >
.
- Prev by Date: RE: An error occurred while attempting to access the SSO database.
- Next by Date: Re: Matching Output and Input message ids
- Previous by thread: Re: ordered delivery
- Next by thread: error msg "worker threaded, reported failure, class not regestered in biztalk
- Index(es):
Relevant Pages
|
