camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Babak Vahdat (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4498) camel websocket component
Date Fri, 06 Jan 2012 18:02:39 GMT


Babak Vahdat commented on CAMEL-4498:


You're absolutely right! Nothing is wrong in the svn repo, The problem is the local workspace
of *me & yours*.

If you would do a

mvn clean install eclipse:clean eclipse:eclipse idea:clean idea:idea

And then again do the

svn status

You will see lots of outgoing changes, which should be *ignored*. If you add them to the svn
ignore list (for example using your IDE) then the next scv update would *ignore* them while
it compares *your* local workspace content with the repository content.

> camel websocket component
> -------------------------
>                 Key: CAMEL-4498
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.9.0
>            Reporter: Christopher Köster
>            Assignee: Charles Moulliard
>              Labels: features
>             Fix For: 2.9.1, 2.10
>         Attachments: camel-websocket.jpg
> 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