Not able to invoke an orchestration via the Filer Criteria when using a Custom Pipeline

 

 

 

 

 

 

 

 

 

 

When filter criteria is used in the Receive Shape in Orchestration.If we use XML Receive Pipeline the Orchestration is Invoked.But when Custom pipeline is used the Orcehstration is not Invoked.

I analysed the situation.It can be with respect to the Message Part Size which gets reduced when using any Pipeline.

If anybody has any idea please reply .

The code of Custom Pipeline is as follows-:

public

 

IBaseMessage Execute(IPipelineContext pContext,IBaseMessage

pInMsg)

{

 

 

string strTempFileName = System.Configuration.ConfigurationSettings.AppSettings.Get(“AutoPrint_TempFileDirectory”

);

strTempFileName = strTempFileName + pInMsg.MessageID.ToString() +

 

“.txt”;

//Create unique name for Temporary file

 

 

 

XmlTextReader xmlRdr = new XmlTextReader

(pInMsg.BodyPart.GetOriginalDataStream());

 

 

ReadAndRemoveXMLNode xmlRDRTrimmed=new ReadAndRemoveXMLNode

(xmlRdr,strNodeNameOfBase64Contents,strTempFileName);

 

 

//Above Line create object for ReadAndRemoveXMLNode Class

 

 

XmlTranslatorStream translatorStream = new XmlTranslatorStream

(xmlRDRTrimmed);

pInMsg.Context.Write(

 

“AutoPrint”, “http://schemas.veson.com”

, strTempFileName);

pInMsg.BodyPart.PartProperties.Write(

 

“a”

, strSystemPropertiesNS, strMessageType1);

pInMsg.BodyPart.Data = translatorStream;

pInMsg.Context.Promote(

 

“MessageType”

, strSystemPropertiesNS, strMessageType);

 

 

return

pInMsg;