[
https://issues.jboss.org/browse/JBMETA-386?page=com.atlassian.jira.plugin...
]
Tomaz Cerar moved WFLY-4725 to JBMETA-386:
------------------------------------------
Project: JBoss Metadata (was: WildFly)
Key: JBMETA-386 (was: WFLY-4725)
Workflow: classic default workflow (was: GIT Pull Request workflow )
Affects Version/s: 8.1.1.Final
(was: 10.0.0.Alpha2)
Component/s: web
(was: Web (Undertow))
(was: Web Sockets)
Deployment fails when jboss-web.xml contains
<enable-websockets>true</enable-websockets>
----------------------------------------------------------------------------------------
Key: JBMETA-386
URL:
https://issues.jboss.org/browse/JBMETA-386
Project: JBoss Metadata
Issue Type: Bug
Components: web
Affects Versions: 8.1.1.Final
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)