Hi Brian,
Sounds like a bug. Since we never use getChildNodes() internally (it's not
even supported in our default source tree), I'd bet it's never been tested.
Can you create a Bugzilla report and attach a small source code example
that reproduces it?
Thanks!
Dave
|---------+--------------------------->
| | Brian Quinlan |
| | <[EMAIL PROTECTED]|
| | com> |
| | |
| | 03/30/2003 04:47|
| | AM |
| | Please respond |
| | to xalan-dev |
|---------+--------------------------->
>----------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| Subject: XalanNodeList and Xerces DOM
|
>----------------------------------------------------------------------------------------------------------------------------------|
1. Create a XercesDOMParsedSource using XalanTransformer::parseSource
2. Call XercesDOMParsedSource::getDocument()
3. Call ::getChildNodes() on an element in that document
4. Every Node in that XalanNodeList is NULL (but the list size is
correct)
Is this expected behavior? Tracing through
XercesDocumentBridge::mapNode, I noticed:
- theXercesNodeImpl != 0
- m_nodeMap.getNode(theXercesNodeImpl) => 0
- m_mappingMode = false
Which leads to the NULL result.
Cheers,
Brian
