[
https://issues.apache.org/jira/browse/DAFFODIL-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869754#comment-16869754
]
Michael Beckerle commented on DAFFODIL-1638:
--------------------------------------------
The state of the art in the open-source eclipse & ScalaIDE flavor thereof seems
unable to address this problem.
If XML Schema Validation is on, then Eclipse cannot use the relative path
schemaLocation attributes in xs:import or xs:include to find the corresponding
files on the classpath. Nor can the XML catalog simply override them. It
simply doesn't resolve them in a compatible manner. Nor can you put a schema
location identified by a relative path in the XML catalog - it insists on an
absolute path, but those don't appear in any of our DFDL schema files as
schemaLocations. It seems there just is no consensus in the XML world about how
XML Schema schemaLocation is used/resolved, whether it can contain relative
paths or not, etc.
If XML Schema Validation is off, and you add "dfdl.xsd" as an extension for
"regular" XML validation, eclipse seems to not validate the DFDL schemas as if
they were ordinary XML. Even if it did, it would not be treating them as XML
Schemas, and so wouldn't process the includes/imports, so would not have
everything it needs to validate, and it wouldn't know about QName references
and how to validate them. It's not very helpful to validate a DFDL schema as
just an XML document.... well it would help deal with editing and completion,
and validation of properties, but .... in any case, it doesn't work. It seems
eclipse special cases the "xsd" extension no matter what.
> Isolate invalid DFDL schema and XML files so IDEs dont flag them
> ----------------------------------------------------------------
>
> Key: DAFFODIL-1638
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1638
> Project: Daffodil
> Issue Type: Improvement
> Components: Clean Ups, Infrastructure
> Reporter: Michael Beckerle
> Priority: Major
>
> our daffodil source tree has, intentionally, invalid DFDL schema files that
> cause validation to fail for unit test purposes (negative tests). We should
> rename these files so they don't cause the Eclipse (or other) IDE to create
> distracting validation warnings when you have the daffodil source tree open.
> These tests need to explicitly use file names like foo.dfdl.xsd.invalid so
> that the IDE will not view it as a XSD file and try to validate it.
> This will enable a single setup of Eclipse to be used by persons trying to
> author DFDL schemas, who want the XML & XSD validation capabilities turned
> on, and used by persons trying to do daffodil development.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
