cxf-issues mailing list archives

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

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

Akitoshi Yoshida commented on CXF-7276:
---------------------------------------

[~reta] I am sorry for my delay. I'll look at this weekend. When I looked at it a while ago,
I thought we could change atmosphere itself to delay its jsr356 related init code so that
it becomes easier for another framework to use jsr356 with atmosphere. If we have several
options, we can choose one based on its complexity (choosing a less-invasive, simpler option)
and its practicability (choosing an option supporting wider use cases). Thanks a lot for looking
into this.
regards, aki


> 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