On Thu, Sep 13, 2012 at 10:31 AM, Christian Müller <christian.muel...@gmail.com> wrote: > Hello Claus! > > Feel free to grap the ticket. At present I don't work on it and I would be > happy to have this solved soon. >
I have attached a patch to the ticket https://issues.apache.org/jira/browse/CAMEL-4857 This allows component developers to control whether their component should receive - encoded uri as current (default behavior) - raw uri (as typed by end user) There is a slight API addition to org.apache.camel.Component, to allow component writers to tell Camel they want the raw uri. However this ought not to be a problem really, as in Camel 2.9.0 we added a new method as well, and there hasn't been any major issues with that change. I guess almost all people extend DefaultComponent which gives them the default implementations of these methods. The patch in this regard is fully backwards compatible. And I have run a full test locally, and all tests passes. The test case attached in the JIRA ticket now also passes, if raw mode enabled. Any thoughts? -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
