Google Mail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Pipeline Custom component replace string in a edifact
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
Andres Felipe Arguello  
View profile   Translate to Translated (View Original)
 More options 10 Aug 2004, 16:21
Newsgroups: microsoft.public.biztalk.general
From: "Andres Felipe Arguello" <felipe.argue...@cenet.com>
Date: Tue, 10 Aug 2004 10:21:20 -0500
Local: Tues 10 Aug 2004 16:21
Subject: Pipeline Custom component replace string in a edifact
Hi i try to make a custom receive pipeline, to replace some strings in the
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.

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Gilles [MSFT]  
View profile   Translate to Translated (View Original)
(1 user)  More options 10 Aug 2004, 19:44
Newsgroups: microsoft.public.biztalk.general
From: Gil...@online.microsoft.com (Gilles [MSFT])
Date: Tue, 10 Aug 2004 18:44:31 GMT
Local: Tues 10 Aug 2004 19:44
Subject: RE: Pipeline Custom component replace string in a edifact
Hello,

>Hi i try to make a custom receive pipeline, to replace some strings in the
>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.

I am not sure I understand exactly what you are trying to do. It seems that you are trying to replace some strings in a message.
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.

This being said, a common error in writing custom pipelines is to not "rewind" the stream after reading it.
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,

You could post the relevant part of your code here and we would be better able to help you.

Thanks.
-Gilles.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google