[ 
https://issues.apache.org/jira/browse/WSCOMMONS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574454#action_12574454
 ] 

Hiranya Jayathilaka commented on WSCOMMONS-305:
-----------------------------------------------

Simply extending the test to include CDATA elements will solve the problem of 
traversing structures with CDATA tags.

public String getText() {
        String childText = null;
        StringBuffer buffer = null;
        OMNode child = this.getFirstOMChild();

        while (child != null) {
            if (child.getType() == OMNode.TEXT_NODE || child.getType() == 
OMNode.CDATA_SECTION_NODE) {
                OMText textNode = (OMText) child;
                String textValue = textNode.getText();
                ............. 

> OMElementImpl.getText() returns an empty String for text in CDATA tags
> ----------------------------------------------------------------------
>
>                 Key: WSCOMMONS-305
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-305
>             Project: WS-Commons
>          Issue Type: Improvement
>          Components: AXIOM
>         Environment: any
>            Reporter: Hiranya Jayathilaka
>
> AXIOM supports building OM structures with CDATA elements. For an example 
> something like,
> soapFactory.createOMText(parentNode, "some text",XMLStreamConstants.CDATA);
> is perfectly valid and delivers the expected result. But when traversing such 
> an OM structure calling parentNode.getText() returns an empty String. Instead 
> it would have been better if it returned the String without the CDATA tags. 
> For an example calling getText() on an element like,
> <parentnode><![CDATA[some text]]></parentnode>
> should return the String, "some text".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to