[ http://issues.apache.org/jira/browse/AXIS2-74?page=comments#action_12318978 ]
Jayachandra Sekhara Rao Sunkara commented on AXIS2-74: ------------------------------------------------------ Hi! I've run the XMLConformance test. This time parse count is 735 while succes count is 558. I've tried to see what are the reasons and found out the following. We are building OM out of the given xml but are just serializing back only the DocumentElement, hence many xml files that had DTD elements and document level PIs are not getting fully serialized in the emitted out xml from om model. This is reducing the success rate significantly. We successfully got during OM building phase DTD elements, PI s etc all as children inside the OMDocument. Its just that we are not serializing them out that is lessing the success rate. In the test case I modified the existing code to serialize the whole OMDocument rather than just the DocumentElement, however there wasn't any improvement in the success rate because internally inside OMDocumentImpl.serialize() method only the rootElement is being serialized rather than all the children. Can the OMDocumentImpl.serialize() method be revisited by someone to incorporate serializing of all the children (just the way OMElementImpl.serialize() does)? I guess, some util functions argument types might have to be changed to reuse code for this purpose. Jaya > Full Infoset support in AXIOM > ----------------------------- > > Key: AXIS2-74 > URL: http://issues.apache.org/jira/browse/AXIS2-74 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: om > Reporter: Davanum Srinivas > Assignee: Jayachandra Sekhara Rao Sunkara > Priority: Minor > Attachments: PInCommentImplModify.patch > > Jaya, > With latest SVN the conformance output is as follows: > File count is 832 > Parsed count is 774. This is just partial success > Complete success count is 466 > Can you please spend some time to resolve other problems? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
