This is because PTT build the message only for predefined handlers such as Security which is added in 'InFlow'. <handler name="RelaySecuirtyMessageBuilderDispatchandler"
class="org.apache.synapse.transport.passthru.util.RelaySecuirtyMessageBuilderDispatchandler"/> We can create a BAM specific handler for the same purpose, or create a generic handler which we can invoke if a given module is engaged (similar to security/tracing). On Mon, Aug 5, 2013 at 4:38 PM, Balakrishnan Gokulakrishnan <[email protected]>wrote: > Hi, > > We were testing the BAM service data agent in ESB 4.7.0 and noticed that > for some reason SOAP headers are not being recognized. Basically when a > custom SOAP header is set and sent the Axis2 handler in the service data > agent cannot see that header. However, the header can be seen at the > Synapse message context and can be printed through a log mediator. > > This behaviour could be observed in the passthru transport but not in NIO > nor servlet transports. > > What could be the reason for this behaviour? > > Thanks, > Gokul. > > -- > *Balakrishnan Gokulakrishnan* > Software Engineer, > WSO2, Inc.; http://wso2.com > > Twitter: http://twitter.com/gokulbs > Mobile: +94775935789 > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
