[jira] Commented: (LOG4NET-34) Allow xml config values to be set via XmlNodeType.CDATA or XmlNodeType.Text rather than just value=foo

[ http://issues.apache.org/jira/browse/LOG4NET-34?page=comments#action_12313844 ] Nicko Cadell commented on LOG4NET-34: - Multiple CDATA sections will be concatenated together on a single line. Empty text nodes will be ignored (by the parser). To embed

[jira] Resolved: (LOG4NET-34) Allow xml config values to be set via XmlNodeType.CDATA or XmlNodeType.Text rather than just value=foo

[ http://issues.apache.org/jira/browse/LOG4NET-34?page=all ] Nicko Cadell resolved LOG4NET-34: - Fix Version: 1.2.10 Resolution: Fixed I have applied the patch with mods and all is well Allow xml config values to be set via XmlNodeType.CDATA

[jira] Created: (LOG4NET-34) Allow xml config values to be set via XmlNodeType.CDATA or XmlNodeType.Text rather than just value=foo

Allow xml config values to be set via XmlNodeType.CDATA or XmlNodeType.Text rather than just value=foo Key: LOG4NET-34 URL: http://issues.apache.org/jira/browse/LOG4NET-34

NamespaceFilter.cs

I created the following filter for filtering on namespaces. It was a simple change from StringMatchFilter filter. I am sure this can be improved on, I'm not even sure it will work if your binary is compiled in release mode. I figured I would forward it along if anyone else needs of if you want

Re: NamespaceFilter.cs

I think the filter would be more useful if it dealt with the LocationInfo object instead of just the ClassName: filter type=LocationInfoStringMatchFilter stringToMatch locationInfoProperty=ClassName value=Foo / /filter filter type=LocationInfoStringMatchFilter stringToMatch