[
https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-24960:
-------------------------------------
The recent changes I was referring to was updating the bundled schema in our catalog with
all those found in eap 7.1 cr2. So if there were some schema that weren't bundled,
they should be there now.
After re-reading the issue, it seems clear that this is a problem with the quickstart
itself. The example xml file provided with the quickstart does not provide a grammar. This
doesn't seem an error with jbt / devstudio / eclipse at all. It is not erroring
"inconsistently". It is erroring because the given xml file has no grammar or
namespace associated with it.
This should be fixed in the quickstart.
JBDS 11 produces warnings about missing schemas inconsistently
--------------------------------------------------------------
Key: JBIDE-24960
URL:
https://issues.jboss.org/browse/JBIDE-24960
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html-source-editing
Affects Versions: 4.5.0.Final
Reporter: Michal Jurc
Assignee: Rob Stryker
Fix For: 4.5.1.Final
The following warning is produced by JBDS11 consistently upon import of
{{ejb-security-jaas}} quickstart:
||Description||Resource||Path||Location||Type||
|No grammar constraints (DTD or XML Schema) referenced in the
document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem|
The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}),
however no such warning is produced unless the user selects the file to validate it.
This is inconsistent, confusing and it is not at all obvious where the JBDS is taking
schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any
application using Elytron client with EAP7.1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)