[
https://issues.apache.org/jira/browse/WSCOMMONS-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved WSCOMMONS-370.
--------------------------------------
Resolution: Fixed
684312
> Add more servicability to OMStaxWrapper
> ---------------------------------------
>
> Key: WSCOMMONS-370
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-370
> Project: WS-Commons
> Issue Type: Improvement
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> Axiom exposes an XMLStreamReader interface. The implementation of this
> interface is the OMStAXWrapper object.
> The OMStAXWrapper simulates the XMLStreamReader event model by a
> combination of walking the om, walking OMDataSource objects, and getting
> events from the original parser. There are a number of things that can go
> wrong. Sometimes the problems are outside of Axiom (ie. invalid parser or
> incorrectly coded OMDataSource implementation).
> Problem:
> When problems arise due to bad events from OMStAXWrapper, the problems may
> not be detected until much further downstream. This can make it difficult
> to determine the root cause of certain kinds of problems. (Example
> WSCOMMONS-369).
> Solution:
> I am working on a simple OMXMLStreamReaderValidator. When debug is
> enabled, the validator wraps the OMStAXWrapper and can be used to validate
> the events. The first generation of the validator will simply ensure that
> the START_ELEMENT events have a matching END_ELEMENT event.
> If the validator discovers a problem, it logs the assertion failures. This
> new debug information will make it easier to track down the root cause.
> The validator will only be inserted if tracing is enabled. Thus it will not
> affect the performance of axiom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
