[
https://issues.apache.org/jira/browse/AXIOM-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070714#comment-13070714
]
Hudson commented on AXIOM-299:
------------------------------
Integrated in ws-axiom-trunk #458 (See
[https://builds.apache.org/job/ws-axiom-trunk/458/])
AXIOM-311: Refactored the test case for AXIOM-299, taking into account the
new API defined by AXIOM-353.
veithen :
Files :
* /webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/pom.xml
*
/webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/java/org/apache/axiom/ts/om/builder/TestStandaloneConfiguration.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/java/org/apache/axiom/om/OMDTDTest.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/resources/web_w_dtd2.xml
*
/webservices/commons/trunk/modules/axiom/modules/axiom-testsuite/src/main/java/org/apache/axiom/ts/OMTestSuiteBuilder.java
*
/webservices/commons/trunk/modules/axiom/modules/axiom-tests/src/test/resources/web_w_dtd2.xml
> StAXUtils: Add Network Detached XMLStreamReader capability
> ----------------------------------------------------------
>
> Key: AXIOM-299
> URL: https://issues.apache.org/jira/browse/AXIOM-299
> Project: Axiom
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Andreas Veithen
> Fix For: 1.2.8
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
