[
https://issues.apache.org/jira/browse/DAFFODIL-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Beckerle resolved DAFFODIL-78.
-----------------------------------
Resolution: Fixed
Unclear when this got fixed, but the offending test schemas do not have this
referential integrity error any more.
In addition we don't worry about Eclipse support any longer.
There are a variety of tests of referential integrity of intra schema
references between schema components.
> Eclipse support not flagging validation error in DFDL schemas
> -------------------------------------------------------------
>
> Key: DAFFODIL-78
> URL: https://issues.apache.org/jira/browse/DAFFODIL-78
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Mike Beckerle
> Priority: Minor
>
> Our test schemas (AA.dfdl.xsd to BG.dfdl.xsd) are full of a referential
> integrity error.
> They use the default unprefixed namespace as the XSD namespace, but then also
> assume intra-schema references can use unqualified names. This is an error.
> There are two other bugs related. One is that Daffodil itself is validating
> the incoming schemas, and not catching this error. Another is that the
> example schemas have the error and need to be fixed.
> This bug is that Eclipse's schema support *also* isn't finding this error. A
> fix would be to figure out eclipse settings or changes to the XMLSchemaSubset
> schema that will make it really catch these errors for us interactively when
> editing the schemas. This may be as simple as setting some option we're not
> setting currently, or it could turn out to not be possible to fix.
> Example:
> <schema xmlns="http://www.ogf.org/dfdl/dfdl-1.0/XMLSchemaSubset";
> targetNamespace="http://example.com";>
> <element name="foo" type="bar"/><!-- IS THIS LEGAL, no prefix on name of the
> type. -->
> <complexType name="bar">
> <sequence/>
> </complexType>
> </schema>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
