You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2008/09/30 15:43:44 UTC
[jira] Commented: (WSCOMMONS-394) StAXUtils: Add Network Detached
XMLStreamReader capability
[ https://issues.apache.org/jira/browse/WSCOMMONS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635748#action_12635748 ]
Davanum Srinivas commented on WSCOMMONS-394:
--------------------------------------------
Sounds good Rich.
> StAXUtils: Add Network Detached XMLStreamReader capability
> ----------------------------------------------------------
>
> Key: WSCOMMONS-394
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-394
> Project: WS-Commons
> Issue Type: Improvement
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JSR 173 (StAX) Specification did not do an adequate job defining the semantics for processing DTD DOCTYPE constructs.
> The reference implementation's getValue() returns the entire subset of the DOCTYPE instead of returning the instance (docinfo) information.
> This is a known issue and has been discussed on the forum.
> http://markmail.org/message/im6f2yu2y544k3he
> The problem is worse if the DOCTYPE references as external location. To get the subset, the parser implementation must do a network call.
> This is (a) ill-performant and (b) requires the application to be attached to a network.
> In addition, the various parser implementations have different mechanisms for getting the DOCTYPE subset. Some implementations apparently defer
> the processing until the getText() call...while other implementations load the subset when the tag is processed.
> Problem Scenario:
> Configuration and deployment files (i.e. web.xml) often contain DOCTYPE constructs. In many situations, the deployer may not be connected to the
> network when processing the file. In such a scenario, the deployer needs a mechanism to process the file without being hindered by the DOCTYPE
> processing.
> Solution:
> The proposed solution is to add new methods to StAXUtils:
> XMLStreamReader getNetworkDetachedXMLStreamReader(...)
> A caller (i.e. a deployer application) can use the new methods to safely obtain an XMLStreamReader that is configured for a network detached environment.
> As StAX changes, we can update the implementation of the methods.
> Next Action:
> I am working on the proposed solution and tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.