Hi Willem,
Thanks for pointing that out. I couldn't quite use CamelContextFactoryBean
easily (due to not having an application context) but it pointed me in the
right direction at least, found that what I needed was:
protected CamelContext getCamelContext(ComponentContext
componentContext)
Hi,
I have had some issues around content encodings, specifically gzipped HTTP
content for an RSS feed. This is related to:
http://camel.465427.n5.nabble.com/Error-with-RSS-component-accessing-gzip-content-td1335918.html#a1543487
but also separate.
When using either HTTP or HTTP4 components
Hi,
In the upgrade from camel 2.2.0 to 2.4.0 there was a refactoring of OSGi
support. One change was the deprecating of the camel-osgi component in
favor of camel-spring. I am not using spring as such in my application
(obviously certain parts do use it but it isn't a spring based application).
Bryce
On Tue, Jul 20, 2010 at 1:25 PM, Willem.Jiang [via Camel] <
ml-node+1543487-1672642491-53...@n5.nabble.com
> wrote:
> Hi Bryce,
>
> Bryce Ewing wrote:
> > Hi,
> >
> > I have been having a look at the http4 component source and thinking
> about
>
Hi,
I have been having a look at the http4 component source and thinking about
how much of this would end up being duplicated into the RSS component to
properly handle all cases, etc. HttpProducer.extractResponseBody and
utilising GZIPHelper.uncompressGzip seems to cover my particular case.
This
Hi,
I have found at least one site that responds to a request for their RSS feed
with gzipped content, without being asked to. If you request the URL using
curl (with no options) you get binary (gzipped) data back if you use curl
--compressed then curl expects this and displays the content in as
