1.4.0 wasn't coded to use a strategy class so I had to modify the component for the Proof of Concept I'm working on. It would indeed be a useful improvement to allow injection of a filter strategy object. Would you like me to add another JIRA ticket for such an improvement? How about an enhancement ticket for the OSGi HTTP Service producer endpoint?
Regards, Michael Claus Ibsen wrote: > > Hi > > We might need to expose some kind of easier injection / alternation of the > xxxHeaderFilterStrategyt the endpoint is configured with. So end users as > in this case easily can customize it. In some cases end-users doesn't want > to filter all headers, and in others they do. > > It should be easily configurable from spring XML as well. Quickly looking > at the http component you need to alter the HttpComponent to set your own > HttpHeaderFilterStrategy. I think it should be configurable on the > endpoint, then end users can set a URI option, or a setter on the endpoint > itself. Then it's easily configurable in Spring as well. > > > > Med venlig hilsen > > Claus Ibsen > ...................................... > Silverbullet > Skovsgårdsvænget 21 > 8362 Hørning > Tlf. +45 2962 7576 > Web: www.silverbullet.dk > -----Original Message----- > From: Willem Jiang [mailto:[EMAIL PROTECTED] > Sent: 17. september 2008 01:46 > To: [email protected] > Subject: Re: Proxying web services > > Hi Micheal, > > The CAMEL-766[1] will explain this stripping for handling the > "ProtocolHeaders". > You can override the HttpHeaderFilterStrategy yourself and inject it > into the http component. > > [1] https://issues.apache.org/activemq/browse/CAMEL-766 > > Willem > > -- View this message in context: http://www.nabble.com/Proxying-web-services-tp19498936s22882p19535288.html Sent from the Camel - Users mailing list archive at Nabble.com.
