[
https://issues.apache.org/jira/browse/DAFFODIL-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219244#comment-17219244
]
Mike Beckerle commented on DAFFODIL-2422:
-----------------------------------------
If I understand this correctly, this feels high-priority to fix. Without this
you can't, for example, plug a SAX-based EXI writer into the Daffodil parser,
nor a SAX-based EXI-source into the Daffodil unparser. That was a key goal
for the whole SAX-API capability.
> Implement allowed features for DaffodilXMLReader/DaffodilOutputContentHandler
> ------------------------------------------------------------------------------
>
> Key: DAFFODIL-2422
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2422
> Project: Daffodil
> Issue Type: Bug
> Components: API
> Reporter: Olabusayo Kilo
> Priority: Major
>
> The DaffodilXMLReader reader allows you to set/get the
> Namespace/Namespace-Prefixes features, but it actually doesn't implement them
> when passing info to a ContentHandler, as is required by the documentation.
> Since the XMLReader is expected to work with any ContentHandler, this can
> lead to unexpected results. We need to update the XMLReader to send the
> appropriate stuff to the ContentHandler (which within our implementation is
> via the SAXInfosetOutputter), and to mimic the behavior expected of it in the
> [XMLReader Documentation
> title|https://docs.oracle.com/javase/7/docs/api/org/xml/sax/XMLReader.html]
>
> The table is an excerpt from the [SAX Documentation|#package_description]]
> ||Feature ID||Access||Default||Description||
> |namespaces|_read/write_|true|A value of "true" indicates namespace URIs and
> unprefixed local names for element and attribute names will be available.|
> |namespace-prefixes|_read/write_|false|A value of "true" indicates that XML
> qualified names (with prefixes) and attributes (including _xmlns*_
> attributes) will be available.|
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
