XML parser configuration does not handle colon (:) in node/element names


Author
Message
radix
radix
New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)New Member (37 reputation)
Group: Forum Members
Posts: 4, Visits: 8
I'm evaluating v2.6.3, and creating a custom XML Parser.
Using the example for configuring the XML Parser [but with the root node updated to <xml:xxx>], adding any conversion specifier does not create an entry in the column/value table.

To illustrate, here's my Parser Configuration entry with a conversion specifier for 'firstName':
<xml:xxx>
  <name firstName="%S{First}" lastName="Doe"/>
  <employeeId>12345</employeeId>
  <other attr1="ignore">ignore</other>
  <dateJoined>2014-05-16 10:50:14,125</dateJoined>
</xml:xxx>

The example works fine without the ':xxx' in the node name.
Background: I am trying to create a custom parser for Log4jXml, extended to include call-site and exception details. Nodes and elements in this format all begin with 'log4j:'.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Threaded View
Threaded View
radix - 3 Years Ago
LogViewPlus Support - 3 Years Ago
radix - 3 Years Ago
LogViewPlus Support - 3 Years Ago
radix - 3 Years Ago
                         Hi Radix, I just wanted to let you know that we have now released...
LogViewPlus Support - 3 Years Ago
                             Thanks Toby, that seems to work for me now.
radix - 3 Years Ago
                                 Glad to hear it Radix - thanks for letting me know!
LogViewPlus Support - 3 Years Ago

Similar Topics

Login

Explore
Messages
Mentions
Search