On Fri, May 22, 2009 at 7:01 PM, harinair <[email protected]> wrote: > > Claus: > > routerDeliveryChannelAQueue is a Sun MQ. >> But the processor job you do will of course also do the trick and >> remove the unwanted ones from SUN MQ. > > Claus, I think you did not get what I was trying to say. The unsafe message > was not present in the Pipeline! I did: > Message message= exchange.getIn(); > > Now I retrieved the message.getHeaders and iterated through it. I even did > logging of all header names. Still I could not find these "special" headers. > That brought up my original question: if it was not in the headers, then > from where did it come from? Have you checked Exchange properties?
Anyway attaching a debugger to your code in the prcessor, then you can inspect the exchange. The tracer is also suitable to log the message how they are routed in Camel. You can control how much it should log etc. http://camel.apache.org/tracer.html > > Hari Gangadharan > Architect, Globalstar / SPOT > http://www.harinair.com > > > > > > > Claus Ibsen-2 wrote: >> >> Is the endpoint "routerDeliveryChannelAQueue" a Sun MQ queue? >> >> When Camel consumes a message from JMS and you route it somewhere, the >> headers will often also be sent along the payload, if the transport in >> question supports that. For instance HTTP does. And since the original >> message is JMS based I guess the javax.jms.Message object can return >> SUN specific headers when asked for all the headers. >> >> Many of the components in Camel have a HeaderFilterStrategy where you >> can define which headers you want to pass or not. So you could >> configure the http component to use your version of a >> HeaderFilterStrategy to only pass a certain few http headers you like. >> >> But the processor job you do will of course also do the trick and >> remove the unwanted ones from SUN MQ. >> >> >> >>> >>> >>> <route errorHandlerRef="dataPushErrorHandler"> >>> <from ref="routerDeliveryChannelAQueue" /> >>> <process ref="securityHeaderGenerator" /> >>> <to ref="routerLogDefault" /> >>> <recipientList> >>> <xpath resultType="java.lang.String">$routerRoute</xpath> >>> </recipientList> >>> <to uri="bean:responseVerificationProcessor?method=process" /> >>> </route> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Unsafe-Headers-present-in-HTTP-Component-tp23661949p23661949.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >>> >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> >> > > -- > View this message in context: > http://www.nabble.com/Unsafe-Headers-present-in-HTTP-Component-tp23661949p23674532.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
