[
https://issues.apache.org/jira/browse/CAMEL-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697332#comment-16697332
]
ASF GitHub Bot commented on CAMEL-12954:
----------------------------------------
rmannibucau commented on issue #2631: CAMEL-12954 adding camel-websocket-jsr356
module
URL: https://github.com/apache/camel/pull/2631#issuecomment-441281022
For the record myCamel comes from OSGI-INF and
org.ops4j.pax.tinybundles.core.intern.AsyncRawBuilder#build should include it,
i'm checking what is broken for me locally. Now for the real cause I suspect
camel needs to be built twice and not once cause of what it generates during
the first build.
Now the karaf itest passes for websocket-jsr356 test :).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add a camel-websocket component 100% using only JSR356
> ------------------------------------------------------
>
> Key: CAMEL-12954
> URL: https://issues.apache.org/jira/browse/CAMEL-12954
> Project: Camel
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
> Priority: Major
> Fix For: Future
>
>
> Goal is to rely on the standard javax specification and not require to setup
> Atmosphere in containers which now support it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
