cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7276) Atmosphere init code should be moved out of AtmosphereWebSocketServlet Destination
Date Fri, 07 Apr 2017 09:01:42 GMT

    [ https://issues.apache.org/jira/browse/CXF-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960520#comment-15960520
] 

Sergey Beryozkin commented on CXF-7276:
---------------------------------------

Hi Aki, good to hear from you :-), 
looks like what Andriy did is effective, the demo started working with Tomcat 8, the changes
outside of the Atm destination are quite neutral and might in principle benefit other destinations
requiring ServletConfig at the initialization stage.

Thanks, Sergey

> Atmosphere init code should be moved out of AtmosphereWebSocketServlet Destination
> ----------------------------------------------------------------------------------
>
>                 Key: CXF-7276
>                 URL: https://issues.apache.org/jira/browse/CXF-7276
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>            Reporter: Sergey Beryozkin
>            Assignee: Andriy Redko
>
> Unfortunately, moving Atmosphere initialization code out of the AtmosphereWebSocketServletDestination
may not be possible at the moment. As we have discovered, Atmosphere has following constraints:
>   - needs ServletConfig to initialize properly (and leverage f.e. JSR-356 support)
>   - the ServetConfig instance is not available yet at the moment when Destination / DestinationRegistry
are being created / initialized
> In order to somehow workaround that, the suggestion is to introduce interface `ServletConfigAware`
so `AtmosphereWebSocketServletDestination` will implement it. In turn, `CXFNonSpringServlet`
is going to notify all interested destination when the instance of `ServletConfig` becomes
available. At this time, we are able to (re)initialize the `AtmosphereFramework` with JSR-356
support if available. With that, CXF WebSocket transport could be run on Tomcat 8+ natively.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message