What's the best way to parse/process an org.w3c.dom.Element in 2.2.0? #694
Replies: 5 comments 6 replies
-
@mariussoutier can you guess which pull request could have introduced this change? See |
Beta Was this translation helpful? Give feedback.
-
@mariussoutier please try replacing
with
|
Beta Was this translation helpful? Give feedback.
-
I do not think this is the issue. The overridden reader is used in
where it is configured, stashed into The issue that you are seeing seems to be caused by the following:
This looks like a bug in This Xalan bug can be worked around by overriding one method on the
|
Beta Was this translation helpful? Give feedback.
-
@mariussoutier did you have a chance to verify that the above approach works for you? Thanks! |
Beta Was this translation helpful? Give feedback.
-
Glad it worked!
There are two things that look weird: one is the |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm using Akka to parse XML from a streaming response, and in particular
XmlParsing.subtree()
to process subtrees.subtree()
returns anorg.w3c.dom.Element
. Up until ScalaXML 2.1.0, the following was working perfectly:However in ScalaXML 2.2.0 a couple of change have broken this approach. Especially the endDocument() method now tries to access the current XML reader, which doesn't exist in my approach. I've also tried setting the XML reader (DOM2SAX is one) manually, but to no avail. I guess my approach is not the intended use of ScalaXML/FactoryAdapter.
Is also don't understand why the FactoryAdapter is always using its
private var xmlReader: Option[XMLReader]
(FactoryAdapter:225) and not falling back to the overridabledef reader: XMLReader
(XMLLoader:51).Is there another way to do this?
Beta Was this translation helpful? Give feedback.
All reactions