order of attributes in web-app node of web.xml seems to matter with JBoss 6 M2

[mpscholz]

Hi,

I've noticed that the order of the attributes in the top-level <web-app> node in the web-xml of a web application that gets deployed into a JBoss 6 server seems to matter:

Deploying to JBoss 6 M2  a web app with a web.xml that starts with

<web-app  xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">

works fine.

Changing the node to

<web-app  version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

(i.e., simply moving the version node to be the first attribute instead of the last), though, triggers a org.jboss.xb.binding.JBossXBRuntimeException on deployment, stating "Element {http://java.sun.com/xml/ns/javaee}web-app is not bound to a global element".

This has not been the case with JBoss 5 (and version 2.5), has it?

Did someone encounter a similar behavior?

Tested with JBoss JBossAS [6.0.0.20100216-M2 (build: SVNTag=JBoss_6_0_0_20100216-M2 date=20100216)].

[jaikiran]

Try this

<web-app xmlns="http://java.sun.com/xml/ns/javaee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee web-app_3_0.xsd"
      version="3.0">

[mpscholz]

As said above, placing the version attribute at the end of the web-app node works fine for me.

But I thought the order of the attributes should not matter?

[jaikiran]

I copy pasted your exact same file contents into an app of mine:

<?xml version="1.0" encoding="UTF-8"?>
<web-app  version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee  http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
  <display-name>Web Application</display-name>
    
</web-app>

Worked fine on 6.0.0.M2:

21:30:56,823 INFO  [TomcatDeployment] deploy, ctxPath=/test
...
21:30:57,103 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.20100216-M2 (build: SVNTag=JBoss_6_0_0_20100216-M2 date=20100216)] Started in 22s:935ms

Can you post the entire exception stacktrace you are running into?

[mpscholz]

After doing some more tests, I have come to the conclusion that it's in fact not a matter of the order of the version tag (as it appeared to me initially), but of some other interaction of circumstances (most presumably an incorrect ear file containing the same web components lingering around in the deployment directory in addition to the war file in question).

Sorry.

So this thread might be closed.