[
https://issues.apache.org/jira/browse/IGNITE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408142#comment-15408142
]
Pavel Tupitsyn commented on IGNITE-1629:
----------------------------------------
The following logic implemented:
1) If there is NO user-defined logger in .NET:
* Java side works as before, logging to a logger defined in Spring or the
default one
* .NET delegates logging to Java
2) If there is user-defined logger in .NET:
* PlatformLogger is set in Java on startup. Java delegates all logging to .NET
* .NET logs directly to the user logger
This way we have the old behavior by default (File + Console or
Spring-configured). And logs from both .NET and Java are combined in one place
(either in .NET or in Java, depending on configuration).
> .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
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> 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)
