|
Home > Archive > BizTalk Server General > August 2004 > Disassemble Stage Problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Disassemble Stage Problem
|
|
| Roger Austin 2004-08-18, 5:52 pm |
| I am trying to use two flatfile disassembler components in the disassemble
stage of a receive pipeline. The first recognises comma separated files, the
second recognises tab separated files.
At runtime if I feed a comma separated file into the pipeline its works as
expected. If however I feed a tab separated file into the pipeline, I get an
error saying >Unexpected data found while looking for ","<. It then
terminates.
The disassemble stage is a first match stage meaning that the first
component satisfying the selection condition is executed. I would have
assumed that if the first component does not recognise the message format it
would pass it onto the next component. Why is the first component failing and
NOT passing the message on to the next component?
--
Roger
| |
| Matt Milner 2004-08-18, 5:52 pm |
| I had this same problem with the flat file disassembler because it does not
appear to do a very thorough test of the source to see if it matches the
schema, just if it is a flat file. I wrote a custom disassembler that
derived from the flat file one and overrode the Probe method to do my own
probing. In your case, you'd be able to probe for the comma and return true
only if you were dealing with your comma delimited file. You could get
fancier and more robust by checking the doc spec for the delimiter and then
only returning true if you found that.
Matt
"Roger Austin" <RogerAustin@discussions.microsoft.com> wrote in message
news:756FD381-AA6C-467D-8D44-50F111330931@microsoft.com...
> I am trying to use two flatfile disassembler components in the disassemble
> stage of a receive pipeline. The first recognises comma separated files,
the
> second recognises tab separated files.
>
> At runtime if I feed a comma separated file into the pipeline its works as
> expected. If however I feed a tab separated file into the pipeline, I get
an
> error saying >Unexpected data found while looking for ","<. It then
> terminates.
> The disassemble stage is a first match stage meaning that the first
> component satisfying the selection condition is executed. I would have
> assumed that if the first component does not recognise the message format
it
> would pass it onto the next component. Why is the first component failing
and
> NOT passing the message on to the next component?
>
> --
> Roger
| |
| Roger Austin 2004-08-19, 2:48 am |
| Matt thanks. This would obviously be the way I need to go.
I would have thought that any component supplied as part of BizTalk would
behave correctly and attempt to properly match the chosen schema against the
incoming data, and not fall over horribly in this way. This is especially
surprising since anyone new to BizTalk is going to be trying things out with
the supplied components and would expect them to work sensibly. Any comments
MSFT?
"Matt Milner" wrote:
> I had this same problem with the flat file disassembler because it does not
> appear to do a very thorough test of the source to see if it matches the
> schema, just if it is a flat file. I wrote a custom disassembler that
> derived from the flat file one and overrode the Probe method to do my own
> probing. In your case, you'd be able to probe for the comma and return true
> only if you were dealing with your comma delimited file. You could get
> fancier and more robust by checking the doc spec for the delimiter and then
> only returning true if you found that.
>
> Matt
>
>
> "Roger Austin" <RogerAustin@discussions.microsoft.com> wrote in message
> news:756FD381-AA6C-467D-8D44-50F111330931@microsoft.com...
> the
> an
> it
> and
>
>
>
| |
| Narasimhan Padmanabhan 2004-08-27, 6:07 pm |
| Your feedback has been noted.
Thanks!
--------------------
|>>Thread-Topic: Disassemble Stage Problem
|>>thread-index: AcSFv1DA7XYPabk2QIaDpql/RMgnaw==
|>>X-WBNR-Posting-Host: 129.227.52.9
|>>From: =?Utf-8?B?Um9nZXIgQXVzdGlu?=
<RogerAustin@discussions.microsoft.com>
|>>References: <756FD381-AA6C-467D-8D44-50F111330931@microsoft.com>
<OGGtk0WhEHA.2812@tk2msftngp13.phx.gbl>
|>>Subject: Re: Disassemble Stage Problem
|>>Date: Thu, 19 Aug 2004 00:37:01 -0700
|>>Lines: 47
|>>Message-ID: <426451E2-A890-4C62-BA24-75CA423832C1@microsoft.com>
|>>MIME-Version: 1.0
|>>Content-Type: text/plain;
|>> charset="Utf-8"
|>>Content-Transfer-Encoding: 7bit
|>>X-Newsreader: Microsoft CDO for Windows 2000
|>>Content-Class: urn:content-classes:message
|>>Importance: normal
|>>Priority: normal
|>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
|>>Newsgroups: microsoft.public.biztalk.general
|>>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
|>>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
|>>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:18798
|>>X-Tomcat-NG: microsoft.public.biztalk.general
|>>
|>>Matt thanks. This would obviously be the way I need to go.
|>>I would have thought that any component supplied as part of BizTalk
would
|>>behave correctly and attempt to properly match the chosen schema against
the
|>>incoming data, and not fall over horribly in this way. This is
especially
|>>surprising since anyone new to BizTalk is going to be trying things out
with
|>>the supplied components and would expect them to work sensibly. Any
comments
|>>MSFT?
|>>
|>>"Matt Milner" wrote:
|>>
|>>> I had this same problem with the flat file disassembler because it
does not
|>>> appear to do a very thorough test of the source to see if it matches
the
|>>> schema, just if it is a flat file. I wrote a custom disassembler that
|>>> derived from the flat file one and overrode the Probe method to do my
own
|>>> probing. In your case, you'd be able to probe for the comma and
return true
|>>> only if you were dealing with your comma delimited file. You could get
|>>> fancier and more robust by checking the doc spec for the delimiter and
then
|>>> only returning true if you found that.
|>>>
|>>> Matt
|>>>
|>>>
|>>> "Roger Austin" <RogerAustin@discussions.microsoft.com> wrote in message
|>>> news:756FD381-AA6C-467D-8D44-50F111330931@microsoft.com...
|>>> > I am trying to use two flatfile disassembler components in the
disassemble
|>>> > stage of a receive pipeline. The first recognises comma separated
files,
|>>> the
|>>> > second recognises tab separated files.
|>>> >
|>>> > At runtime if I feed a comma separated file into the pipeline its
works as
|>>> > expected. If however I feed a tab separated file into the pipeline,
I get
|>>> an
|>>> > error saying >Unexpected data found while looking for ","<. It then
|>>> > terminates.
|>>> > The disassemble stage is a first match stage meaning that the first
|>>> > component satisfying the selection condition is executed. I would
have
|>>> > assumed that if the first component does not recognise the message
format
|>>> it
|>>> > would pass it onto the next component. Why is the first component
failing
|>>> and
|>>> > NOT passing the message on to the next component?
|>>> >
|>>> > --
|>>> > Roger
|>>>
|>>>
|>>>
|>>
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
|
|
|
|
|