[jira] [Commented] (VYSPER-306) Websocket plugin too tightly bound to Jetty

["Niklas Gustavsson (Commented) (JIRA)" <ji...@apache.org>]

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

Niklas Gustavsson commented on VYSPER-306:
------------------------------------------

Agreed. When I wrote the existing code, Jetty was the only Java app server that implemented web sockets. Now that Tomcat does as well, we should look at redesigning our code to work in a more generic manner. There's also JSR 356 which might make this moot in the future but let's worry about that when it gets done.

If you got a patch for making Vysper work with Tomcat, I'll be happy to review it. Otherwise, I'll have a look at it sometimes in the near future.
                
> Websocket plugin too tightly bound to Jetty
> -------------------------------------------
>
>                 Key: VYSPER-306
>                 URL: https://issues.apache.org/jira/browse/VYSPER-306
>             Project: VYSPER
>          Issue Type: Bug
>          Components: extension
>    Affects Versions: 0.7
>            Reporter: Stig Runar Vangen
>              Labels: extension, websocket
>
> I tried to integrate the websocket plugin into our system. Instead of setting up a jetty endpoint I wanted to use an existing server. This works fine if the server you want to integrate against is a Jetty server. In my case, the server is a Tomcat server. This resulted in Jetty-based errors when accessing the target address. The implementation should be server-independent, so that it could be used in more contexts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira