tag:blogger.com,1999:blog-8073758.post109345062339528174..comments2008-04-02T11:23:55.328-04:00Devdutthttp://www.blogger.com/profile/03111464649546431281noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8073758.post-1135483400660661312005-12-24T23:03:00.000-05:002005-12-24T23:03:00.000-05:00like tumbler and tipsy days hopefully we will remain in high spirits. well, good daymortgage quotehttp://refinance-mortgage-search.comnoreply@blogger.comtag:blogger.com,1999:blog-8073758.post-1112204792460879352005-03-30T12:46:00.000-05:002005-03-30T12:46:00.000-05:00Theoretically speaking you could put the component in any of the 4 sections if you use the:<BR/>[ComponentCategory(CategoryTypes.CATID_Any)]<BR/>attribute for the component. But I'd suggest putting it in the Validate section because the assumption is that AFTER the Disassemble section, the message is more or less in the format that your orchestration subscribes to.Devdutthttp://www.blogger.com/profile/03111464649546431281noreply@blogger.comtag:blogger.com,1999:blog-8073758.post-1112190986693942992005-03-30T08:56:00.000-05:002005-03-30T08:56:00.000-05:00Could u pls let me know where u add the property promoter pipeline component in ur pipeline?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8073758.post-1098386359351074822004-10-21T15:19:00.000-04:002004-10-21T15:19:00.000-04:00Well probably I didn't get your questions correctly, but why would you want to have a UNIFORM Seq Convoy and then have separate branches? Might it be because the messages are of different types? If thats the case, you should look at :<br />http://devdutt10.blogspot.com/2004/09/non-uniform-sequential-convoys-in-bts.html<br />Otherwise you could send me a mail at pyrogenic@hotmail.com, with a more detailed explanation of the question?Devdutthttp://www.blogger.com/profile/03111464649546431281noreply@blogger.comtag:blogger.com,1999:blog-8073758.post-1098368600624775452004-10-21T10:23:00.000-04:002004-10-21T10:23:00.000-04:00Nice, clear examples. Thanks. What about if two branches of a listen shape are each non-uniform sequential convoys (beginning with a activate-receive, init-corr). Branch 1 receives Message1, Message2, Message3, and Branch 2 receives Message2 and Message3. Is there a way to implement a uniform sequential convoy across the branches to prevent a new orch. instance being launched in the event that a Message2 is received that correlates with branch 1?Anonymousnoreply@blogger.com