Hi
We released 2.10.3 in the middle of December 2012.
Since this release we have resolved 78 tickets in JIRA.
https://issues.apache.org/jira/browse/CAMEL/fixforversion/12323558#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
I think its tine we cut a 2.10.4 release fo
Thanks for reporting this, I just fill a JIRA[1] for it.
I think we need to provide the options let the user get control of connection
management.
[1]https://issues.apache.org/jira/browse/CAMEL-6026
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.c
I am getting org.apache.http.conn.HttpHostConnectException exception when i
use the http4 component in routes, but the same routes work fine if i use
the http component.
When i look at the code, i found below method in
org.apache.camel.component.http4.HttpComponen create
ThreadSafeClientConnManag
> That is a good approach.
> ..
> I am waiting for a response.
Great :) Just keep me in the loop.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hi Christian,
I think using the cxf-bean[1] component way can make your life easier.
You can route the request from different transport ( Using embed Jetty or
Servlet) to the cxf-bean component, to the service that you want to expose.
It could be more easy for to manage the transport route by u
Hi,
my blog is focused on WAR/WABs I'm gonna try to add some details on how to
achieve this via the whiteboard extender.
It's gonna take a bit :) If it's not possible now, I'm gonna add it for
Pax-Web 3.0
regards, Achim
2013/1/31 Christian Müller
> Some month ago I was looking for a way to b
Some month ago I was looking for a way to bind camel-cxf to a specific
port, using the OSGI HTTP service.
Achim blogged about binding a web application to a specific port, using the
OSGI HTTP service and an adapted jetty.xml configuration [1]. I'm wondering
whether we can do the same with camel-cxf
Hi Henryk
That is a good approach. I have already contacted the Scomp developer and I am
waiting for a response. Should that not be forthcoming I shall follow your
suggestion.
Regards
Ian
On 31 Jan 2013, at 9:55 AM, "hekonsek [via Camel]"
wrote:
> Hi Ian,
>
> > The original project has not