quote:

---

Originally posted by Matt Milner
Most likely because when you load the xml dom you are reading the stream to
the end so when the message gets to the next stage, there is no data in the
stream. try marking the position of the stream before loading it into the
dom, then reset it after loading.

Also keep in mind that by using the dom, you are limiting your scalability.
Pipeline components really need to use streaming xml interfaces to remain
scalable to large message types.

Matt


"Carloni" <Carloni.15qsiw@mail.webservertalk.com> wrote in message
news:Carloni.15qsiw@mail.webservertalk.com...
>
> Hi there,
>
> I implemented all the component interfaces, and my new pipeline
> component shows up in the toolbox. All it does is change a XML node
> value from the received message.
>
> Here's the code from my component's Disassemble method, which I have
> confirmed is running when I drop in a XML file if I let those lines
> comment. If I Uncomment those lines I'll get the following error:
>
> << The "FILE" adapter is suspending a message coming from Source
> URL:"c:\TrackTrace\FileDrop\*.xml". Details:"Error in accessing the
> part data or one of its fragments. The part or fragment may not exist
> in the database. " >>
>
> Any ideas why Biztalk acts like that ?
>
>
> CODE:
>
> ..
>
> private bool _allMsgSent = false;
> private bool _firstTime = true;
> private XmlDocument inboundXml = new XmlDocument();
> private Stream inboundStream;
> private IBaseMessagePart bodyPart;
> private IBaseMessage bMsg;
>
>
> public new IBaseMessage GetNext(IPipelineContext pContext)
> {
> if (!_allMsgSent)
> {
> if (_firstTime)
> {
> bMsg = base.GetNext(pContext);
> // bodyPart = bMsg.BodyPart;
> // if (bodyPart != null)
> // {
> // inboundStream = bodyPart.GetOriginalDataStream();
> // if (inboundStream != null)
> // {
> // inboundXml.Load(inboundStream);
> // bodyPart.Data = inboundStream;
> // }
> // }
> _firstTime = false;
> }
>
> return bMsg;
> }
>
> return null;
> }
>
>
>
> --
> Carloni
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message211644.html
>

---