[
https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329678#comment-15329678
]
Pavel Tupitsyn commented on IGNITE-1629:
----------------------------------------
Resulting implementation:
* Java: PlatformLogger is set automatically if there is no logger configured
* PlatformLogger delegates everything through JNI. isQuiet always returns false
so that there is no console output in Java
* .NET: Added an ILogger interface and a ConsoleLogger implementation that is
used by default.
* All custom logging (file, windows log, database, etc) is expected to be done
via 3rd party integrations
> .Net: Introduce native logging facility.
> ----------------------------------------
>
> Key: IGNITE-1629
> URL: https://issues.apache.org/jira/browse/IGNITE-1629
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Blocker
>
> This is pretty serious usability issue. Currently Ignite produces logs using
> Java "log4j" library. While naural for Java environment, this is somewhat
> alien for Windows users.
> We need to investigate ability to hack into normal .Net logging frameworks.
> This include both native Windows APIs (e.g. events), and widely-used .Net
> loggers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
