camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Straube (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4498) camel websocket component
Date Tue, 20 Dec 2011 14:09:30 GMT


Claus Straube commented on CAMEL-4498:

Hi Claus,

yes I've seen that on the dev list...

Ok. So we're trying to get into 2.9.1. We've got enough man power to provide what you need
and I think we've a good state at all (except the OSGi stuff). But we need some quicker attention
/ feedback from the core team. Chris opened the issue end of Sept. (incl. code) and the first
reaction was nearly two months later. That's a long time... I know you're all busy people,
but we want to provide a high quality component and for that we need a little bit of your
time ;)

Best regards - Claus       
> camel websocket component
> -------------------------
>                 Key: CAMEL-4498
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.9.0
>            Reporter: Christopher Köster
>              Labels: features
>             Fix For: 2.9.1, 2.10
> We have build an implementation of websockets in Apache Camel. In combination with the
strengths of Apache Camel you can push events from all given components (file, ftp, hazelcast,
queue, etc.) to your browser. This offers great possibilities e.g. in process tracking, process
driven forms and others.
> It is fully bidirectional (in contrast to the AHC-component) and can therefore be used
for producers and consumers. 
> To get a better idea of what has been done so far, please have a look at:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message