[
https://issues.apache.org/jira/browse/CAMEL-10750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890295#comment-15890295
]
James Netherton commented on CAMEL-10750:
-----------------------------------------
Turns out removing this setting seems to cause some issues. I deployed a basic
app to Jetty and TomEE and hit issues unless the SUPPRESS_JSR356 flag was set.
Having thought about things some more, I don't think removing the flag will
help me to integrate with WildFly anyway.
So maybe we close this for now and take another look at how the atmosphere
framework is bootstrapped and configured in future task.
> 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
> Assignee: James Netherton
> Fix For: 2.19.0
>
>
> 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.15#6346)
