You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Stig Runar Vangen (Created) (JIRA)" <ji...@apache.org> on 2012/03/28 11:27:38 UTC
[jira] [Created] (VYSPER-306) Websocket plugin too tightly bound to
Jetty
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
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 errors when 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
[jira] [Updated] (VYSPER-306) Websocket plugin too tightly bound to
Jetty
Posted by "Stig Runar Vangen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stig Runar Vangen updated VYSPER-306:
-------------------------------------
Description: 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. (was: 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 errors when The implementation should be server-independent, so that it could be used in more contexts.)
> 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
[jira] [Commented] (VYSPER-306) Websocket plugin too tightly bound
to Jetty
Posted by "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
[jira] [Closed] (VYSPER-306) Websocket plugin too tightly bound to
Jetty
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed VYSPER-306.
------------------------------------
Resolution: Fixed
Implemented support for Tomcat (and generalized the code in general) in r1328861.
> 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
[jira] [Assigned] (VYSPER-306) Websocket plugin too tightly bound
to Jetty
Posted by "Niklas Gustavsson (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson reassigned VYSPER-306:
----------------------------------------
Assignee: Niklas Gustavsson
> 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
[jira] [Commented] (VYSPER-306) Websocket plugin too tightly bound
to Jetty
Posted by "Stig Runar Vangen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240404#comment-13240404 ]
Stig Runar Vangen commented on VYSPER-306:
------------------------------------------
https://issues.apache.org/bugzilla/show_bug.cgi?id=51181
WebSocket support has been added to Tomcat 7.0.27. Lastest version for download is 7.0.26.
http://java.dzone.com/articles/tomcat-websockets-html5
This guy made an implementation for Tomvat 7.0.14. Provided here as a Tomcat patch.
Based on this, I think it is best to wait until the next Tomcat version is officially released before starting work on a Tomcat implementation. I initially thought of making a wrapper myself on top of the current Servlet API, but this might not be possible.
> 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
[jira] [Commented] (VYSPER-306) Websocket plugin too tightly bound
to Jetty
Posted by "Fabio Mancinelli (Commented) (JIRA)" <ji...@apache.org>.
[ 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