The Apache Jenkins build system has built Camel.trunk.notest (build #1985)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1985/
to view the results.
Hi Charles,
If we only support jetty, that will be fine. But to support tomcat, we
need a component that avoids using jetty's websocket API directly.
In this aspect, camel-cxf is different because its servlet is not
web-container specific and can also be used in a gemini/tomcat based
OSGi environm
+1 for the patch release of 2.11.x and retire the 2.10.x branch after Camel
2.10.7.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
T
Hi Aki,
As the camel-websocket component uses Jetty + WebSocket servlet of Jetty,
that should not be a big change to add a property for the endpoint to
request that we use Jetty deployed in Karaf, Felix, ... instead of creating
a local jetty instance. This is what we do with camel-cxf endpoint
Re
I agree too.
Best,
Christian
Am 10.09.2013 12:59 schrieb "Hadrian Zbarcea" :
> Agree, I'll take care of it this week.
> Hadrian
>
> On 09/10/2013 06:00 AM, Claus Ibsen wrote:
>
>> Hi
>>
>> I think its time we cut a new patch release of 2.11 branch. We have
>> 100+ resolved tickets since last rele
Agree, I'll take care of it this week.
Hadrian
On 09/10/2013 06:00 AM, Claus Ibsen wrote:
Hi
I think its time we cut a new patch release of 2.11 branch. We have
100+ resolved tickets since last release.
And 2.11.1 was released about 2 months ago
http://camel.apache.org/2013/07/17/apache-camel-
Hi
I think its time we cut a new patch release of 2.11 branch. We have
100+ resolved tickets since last release.
And 2.11.1 was released about 2 months ago
http://camel.apache.org/2013/07/17/apache-camel-2111-released.html
So if we get some time then we could consider cutting a patch release
in
I have been looking into the websocket component and I was wondering
about a few things.
First of all, I would like to make the component use the framework's
servlet if it's running in e.g., an OSGi container like karaf that has
jetty or another container that uses geminiweb/tomcat. I was using
A
