[ https://issues.jboss.org/browse/JBIDE-22141?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22141: --------------------------------------- I need some help with verifying this. Just to make it clear, the conclusion is that the original jboss-app.xml from the article is wrong and is not gonna work, correct? The one Rob provided is still wrong as the version needs to be 6. So something that should work is: {code} <?xml version="1.1" encoding="UTF-8"?> <jboss-app version="6" xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jee="http://www.jboss.com/xml/ns/javaee" xsi:schemaLocation=" http://www.jboss.com/xml/ns/javaee http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd"> <description>test</description> </jboss-app> {code} And that will give you: {code} cvc-complex-type.2.4.a: Invalid content was found starting with element 'description'. One of '{"http://java.sun.com/xml/ns/javaee":application-name, "http:// java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/ javaee":display-name, "http://java.sun.com/xml/ns/javaee":icon, "http:// java.sun.com/xml/ns/javaee":initialize-in-order, "http://java.sun.com/xml/ns/ javaee":module}' is expected. {code} And that's what your patch will fix so that the xml above should work, [~rob.stryker] ? Now, how do I try this out in Eclipse? Change it in the catalog bundle? Or if I add the modified xsd in the xml catalog, will that take preference? I tried this and noticed that the patched xsd actually specifies version 7.0, so now I'm confused. With that it seems that actually what should be used is the original xml that Rob provided. But that still tells me that version 7.0 is not defined, even though I added the new xsd to the catalog. [~rob.stryker], please clarify and advice how to test, thanks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)