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:'.

Thanks for the assistance, and I look forward to trying out the beta when released.

For now I'll stick with the built-in Log4XmlParser. Since my log source is UDP, I don't think I can use an open action successfully.

Hi Radix,

I just wanted to let you know that we have now released LogViewPlus v2.6.5 as a BETA release.

This release addresses the XML namespace issue discussed above.

Thanks again for bringing this issue to our attention. Please do let me know if you have any further questions or issues.

Toby

Thanks Toby, that seems to work for me now.

Glad to hear it Radix - thanks for letting me know!