[jboss-jira] [JBoss JIRA] (WFLY-4725) Deployment fails when jboss-web.xml contains <enable-websockets>true</enable-websockets>

Tomaz Cerar (JIRA) issues at jboss.org
Tue Jun 2 09:56:02 EDT 2015


    [ https://issues.jboss.org/browse/WFLY-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073162#comment-13073162 ] 

Tomaz Cerar commented on WFLY-4725:
-----------------------------------

Fails how? can you post stacktrace?

> Deployment fails when jboss-web.xml contains <enable-websockets>true</enable-websockets>
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-4725
>                 URL: https://issues.jboss.org/browse/WFLY-4725
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow), Web Sockets
>    Affects Versions: 10.0.0.Alpha2
>            Reporter: Radim Hatlapatka
>            Assignee: Stuart Douglas
>            Priority: Minor
>
> When deploying application with WebSockets used in EAP 6 to EAP 7, deployment will fail due EAP7 not supporting [1] in jboss-web.xml. The {{<enable-websockets>}} element is required in EAP 6 to enable the WebSockets functionality in JBoss Web.
> This element should be also allowed in EAP 7 in order to simplify migration from EAP 6. Functionality of {{ <enable-websockets>true</enable-websockets>}} can be ignored as in EAP 7 and in Undertow there is no need to enable WebSockets explicitly.
> [1]
> {code:xml}
> <jboss-web version="7.2"
>    xmlns="http://www.jboss.com/xml/ns/javaee"
>    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>    xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee schema/jboss-web_7_2.xsd">
>     <enable-websockets>true</enable-websockets>
> </jboss-web>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list