[jira] Resolved: (OODT-161) PushPull getTextContext()/getNode() value still poses an issue for some JVMs

["Brian Foster (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OODT-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Foster resolved OODT-161.
-------------------------------

    Resolution: Fixed


- fixed in r1082220

> PushPull getTextContext()/getNode() value still poses an issue for some JVMs
> ----------------------------------------------------------------------------
>
>                 Key: OODT-161
>                 URL: https://issues.apache.org/jira/browse/OODT-161
>             Project: OODT
>          Issue Type: Bug
>          Components: push pull framework
>    Affects Versions: 0.2
>         Environment: none
>            Reporter: Brian Foster
>            Assignee: Brian Foster
>            Priority: Minor
>             Fix For: 0.3
>
>         Attachments: OODT-161.2011-03-16.patch.txt
>
>
> this is a two part problem:
> 1) pushpull depends on an older version of nekohtml (which depends on an older version of xercesImpl)
>    - patch will update nekohtml to version: 1.9.6.2
> 2) Node node . . . ; node.getNodeValue() should be node.getChildNodes().item(0).getNodeValue() . . . instead of node.getTextContext().
>    - apparently text inside of a Node object isn't its value . . . the text value desired is stored in the a child node at index 0 whose value is the value desired

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira