FYI，the patch of CAMEL-2950 is applied into camel trunk, please check
out the latest Camel 2.5-SNAPSHOT to verify the fix :)
Willem
----------------------------------
Apache Camel, Apache CXF committer
Open Source Integration http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
Willem Jiang wrote:
Yes, they are the same problem.
Current camel-http component can't deal with the address part rightly.
It should skip the URI which protocal part is not start with http: or
https, in this way we could register a customer protocal name for it.
I just create a JIRA[1] for it.
[1]https://issues.apache.org/activemq/browse/CAMEL-2950
Willem
----------------------------------
Apache Camel, Apache CXF committer
Open SOA http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
Cappa Roberto wrote:
The two versions:
HttpComponent httpComponent = new HttpComponent();
getContext().addComponent("http2", httpComponent);
or
getContext().addComponent("http2", getContext().getComponent("http"));
have the same behaviour when the endpoint is used (the "unsupported
protocol: 'http2'" exception). Probably there is another problem.
Thanks
