You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Fabio Mancinelli (Commented) (JIRA)" <ji...@apache.org> on 2012/04/11 17:19:18 UTC

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

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

Fabio Mancinelli commented on VYSPER-306:
-----------------------------------------

I've created a similar issue for the BOSH plugin, because I think that we have the same problem there (VYSPER-307)
                
> 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
>            Assignee: Niklas Gustavsson
>              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