[
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
