You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (JIRA)" <ji...@apache.org> on 2017/01/26 16:21:24 UTC
[jira] [Updated] (CAMEL-10750) Suppression of JSR356 should be
restricted to Jetty
[ https://issues.apache.org/jira/browse/CAMEL-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Netherton updated CAMEL-10750:
------------------------------------
Description:
We have some logic that sets up the atmosphere websocket config in the WebsocketConsumer.
https://github.com/apache/camel/blame/52a739feb9da8acd29067304c7c8356bbc5ef4dd/components/camel-atmosphere-websocket/src/main/java/org/apache/camel/component/atmosphere/websocket/WebsocketConsumer.java#L53-L54
If suppression of JSR 356 is specific to running on Jetty, why do we enforce it globally?
I'm trying to integrate this component on WildFly so it seems reasonable to me that I should be able to make use of JSR 356.
Maybe we should only apply this restriction if Jetty is detected?
was:
We have some logic that sets up the atmosphere websocket config in the WebsocketConsumer.
https://github.com/apache/camel/blame/52a739feb9da8acd29067304c7c8356bbc5ef4dd/components/camel-atmosphere-websocket/src/main/java/org/apache/camel/component/atmosphere/websocket/WebsocketConsumer.java#L53-L54
If suppression of JSR 356 is specific to running on Jetty, why do we enforce it globally?
I'm trying to integrate this component on WildFly so it seems reasonable to me that I should be able to make use of JSR 356.
Maybe we only apply this restriction if Jetty is detected?
> Suppression of JSR356 should be restricted to Jetty
> ---------------------------------------------------
>
> Key: CAMEL-10750
> URL: https://issues.apache.org/jira/browse/CAMEL-10750
> Project: Camel
> Issue Type: Improvement
> Components: camel-atmosphere-websocket
> Reporter: James Netherton
>
> We have some logic that sets up the atmosphere websocket config in the WebsocketConsumer.
> https://github.com/apache/camel/blame/52a739feb9da8acd29067304c7c8356bbc5ef4dd/components/camel-atmosphere-websocket/src/main/java/org/apache/camel/component/atmosphere/websocket/WebsocketConsumer.java#L53-L54
> If suppression of JSR 356 is specific to running on Jetty, why do we enforce it globally?
> I'm trying to integrate this component on WildFly so it seems reasonable to me that I should be able to make use of JSR 356.
> Maybe we should only apply this restriction if Jetty is detected?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)