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

[Radim Hatlapatka (JIRA)]

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

Radim Hatlapatka commented on WFLY-4725:
----------------------------------------

The schema jboss-web_7_2.xsd is not available in WildFly. And the deployment fails with [1] as it doesn't recognize the enable-websockets element.

Note copying the schema to {{$JBOSS_HOME/docs/schema} from EAP 6.4, it is not sufficient.

{noformat}
6:00:36,049 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."websocket-demo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."websocket-demo.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "websocket-demo.war"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0027: Failed to parse XML descriptor "/content/websocket-demo.war/WEB-INF/jboss-web.xml" at [5,5]
	at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:81)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
	... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,5]
Message: Unexpected element '{http://www.jboss.com/xml/ns/javaee}enable-websockets' encountered
	at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:115)
	at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:280)
	at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:73)
	... 6 more

16:00:36,052 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "websocket-demo.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"websocket-demo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"websocket-demo.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"websocket-demo.war\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0027: Failed to parse XML descriptor \"/content/websocket-demo.war/WEB-INF/jboss-web.xml\" at [5,5]
    Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,5]
Message: Unexpected element '{http://www.jboss.com/xml/ns/javaee}enable-websockets' encountered"}}

{noformat}

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