[ https://issues.jboss.org/browse/JBIDE-20012?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-20012 at 6/10/15 1:51 PM: ------------------------------------------------------------------ I've found two problems here: 1) When validator tries to find CMDocument for the <h:body> element it searches the XML Catalog and finds schema in org.jboss.tools.jsf/taglibs/html_basic.taglib.xml file. But the CMDocument created from this schema doesn't contain elements (which are required to validate <h:body> element against). This schema comes from org.jboss.tools.jsf plug-in. 2) Then I've tried to remove any jsf* plug-ins from Run Configuration and faced the same problem (<h:body> element wasn't validated properly, while clean Eclipse Mars + WTP configuration validates <h:body> tag successfully). In such Run Configuration I've found that there is no schema defined for public ID "http://www.w3.org/1999/xhtml" (which exists in clean Eclipse Mars + WTP installation). So, the validation has started to work properly after I've added the following XML Catalog entry: {code} Entry element: URI Location: http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd URI: http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd Key type: Namespace name Key: http://www.w3.org/1999/xhtml {code} [~akazakov] Can we replace our schema (org.jboss.tools.jsf/taglibs/html_basic.taglib.xml) by the default one from Eclipse JEE bundle? Will it break our own Validation and Content Assist features? PS: I've restored jsf* plug-ins in my Run Configuration (with "http://www.w3.org/1999/xhtml" schema still added) and found that validation for <h:body> works fine. But I have no Content Assist for <h:| and so on (from other side, there was no CA before I added "http://www.w3.org/1999/xhtml" schema also)... was (Author: vrubezhny): I've found two problems here: 1) When validator tries to find CMDocument for the <h:body> element it searches the XML Catalog and finds schema in org.jboss.tools.jsf/taglibs/html_basic.taglib.xml file. But the CMDocument created from this schema doesn't contain elements (which are required to validate <h:body> element against). This schema comes from org.jboss.tools.jsf plug-in. 2) Then I've tried to remove any jsf* plug-ins from Run Configuration and faced the same problem (<h:body> element wasn't validated properly, while clean Eclipse Mars + WTP configuration validates <h:body> tag successfully). In such Run Configuration I've found that there is no schema defined for public ID "http://www.w3.org/1999/xhtml" (which exists in clean Eclipse Mars + WTP installation). So, the validation has started to work properly after I've added the following XML Catalog entry: {code} Entry element: URI Location: http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd URI: http://www.w3.org/2002/08/xhtml/xhtml1-strict.xsd Key type: Namespace name Key: http://www.w3.org/1999/xhtml {code} [~akazakov] Can we replace our schema (org.jboss.tools.jsf/taglibs/html_basic.taglib.xml) by the default one from Eclipse JEE bundle? Will it break our own Validation and Content Assist features? -- This message was sent by Atlassian JIRA (v6.3.15#6346)