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

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar edited comment on JBMETA-386 at 6/2/15 10:12 AM:
-------------------------------------------------------------

Latest metadata parser needs to be updated to account for feature added in jboss-web 7.2


was (Author: ctomc):
Latest metadata parser needs to be updated to account for feature added in 7.2

> 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)