| |
microsoft.public.biztalk.general |
Hello, This being said, a common error in writing custom pipelines is to not "rewind" the stream after reading it. You could post the relevant part of your code here and we would be better able to help you. Thanks.
>edifact file, in the first try, i find that is necessary to implement the
>xml dissasembler and validator, and party ressolution, without that the
>pipeline doesn't work, but when i try to modify the execute method in the
>custom compoenent the system cant change the data in the document and doesnt
>validate.
>Anyone has this issue? or know what im doing wrong? actually the custom
>component i call in the validate just after the xml validate.
Usually, the best place to do this (provided that you do not have any constraint) is in a decoder.
A decoder gets to see the mesasge in the pipeline first. You can change things in here and then leave your existing pipeline
unchanged. This way, party resolution and other things will work.
You should be stream.Seek(0, SeekOrigin.Begin); so the next component can read from the beginning.
However, without looking at your code, this is going to be hard,
-Gilles.