You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Srinath Perera (JIRA)" <ji...@apache.org> on 2005/06/23 05:53:12 UTC

[jira] Assigned: (AXIS2-22) Need for Child API in OMDocument

     [ http://issues.apache.org/jira/browse/AXIS2-22?page=all ]

Srinath Perera reassigned AXIS2-22:
-----------------------------------

    Assign To: Ajith Harshana Ranabahu  (was: Davanum Srinivas)

AFAIK the OMDocument is removed (or to be removed). I do not know about the finer detail arise in the case of full info set support .. Ajith over to you

> Need for Child API in OMDocument
> --------------------------------
>
>          Key: AXIS2-22
>          URL: http://issues.apache.org/jira/browse/AXIS2-22
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: om
>     Reporter: Jayachandra Sekhara Rao Sunkara
>     Assignee: Ajith Harshana Ranabahu

>
> Current OMDocument doesn't have a child API in it. We might be doing away without it
> as far as soap processing is considered. But without the child
> navigation API in OMDocument, XMLInfoset can never be fully supported because
> in an XML document other than the unique root element, at the same
> level we can have several other nodes like documentation comments,
> processing instructions, DTD element etc.
> I will create a patch to incorporate the same and submit it.
> Thanks
> Jayachandra

-- 
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