Here's my favorite way to handle such situations. It can probably be adapted to your situation. https://play.golang.org/p/FQ0g4rytz3
On Wed, Apr 5, 2017 at 4:44 PM Mandolyte <cecil....@gmail.com> wrote: > First, never thought I'd have to parse XML again (it's been over 10 > years), but life happens... > > After a lot of searching I found only few examples using the streaming > API. But I'm not sure the examples will work for me (I'll find out more > tomorrow when I get back to the office). The XML I must parse is deeply > nested with the same element nodes at different levels; it is in general a > bit unpredictable. It is, in essence, a set of rules for rules > engine/wizard. The files are moderate in size; I have seen any over 10K > lines pretty printed yet. > > I need to parse to find a known element, then based on what I find, decode > its children elements. This implies I need to treat the child elements as a > document (may have to add a fake root node, unless the decoder accepts > sequences). But I haven't seen any examples of such an approach. > > Thanks for any advice! > Cecil > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
