Trace:
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
jvx:common:util:loggerfactory [2018/02/02 09:47] admin created |
jvx:common:util:loggerfactory [2024/11/18 10:35] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~Title: Logging using LoggerFactory~~ | + | ~~Title: Logging Using LoggerFactory~~ |
| Without log mechanisms, software development is a lot more arduous than it needs to be. For this reason, a log mechanism is included in JVx. | Without log mechanisms, software development is a lot more arduous than it needs to be. For this reason, a log mechanism is included in JVx. | ||
| Line 38: | Line 38: | ||
| </file> | </file> | ||
| - | JVx´s standard implementation limits the use of loggers. The actual instance of a logger (ILogger) is not initialized until it is accessed, i.e. a log output occurs. | + | JVx´s standard implementation limits the use of loggers. The actual instance of a logger (ILogger) is not initialized until it is accessed, i.e., a log output occurs. |
| The implementation of vararg parameters (Object...) positively affects performance and readability of the source code. The following constructs are not uncommon: | The implementation of vararg parameters (Object...) positively affects performance and readability of the source code. The following constructs are not uncommon: | ||
| Line 103: | Line 103: | ||
| #com.sibvisions.rad.server.level = OFF | #com.sibvisions.rad.server.level = OFF | ||
| - | #javax.rad.level = ALL | + | #jvx.rad.level = ALL |
| </file> | </file> | ||
| Line 114: | Line 114: | ||
| </file> | </file> | ||
| - | JVx´s log implementation can be used for RIAs, Desktop, Web and Android applications. For WebUI applications it should be noted that the log outputs occur at the server. | + | JVx´s log implementation can be used for RIAs, desktop, web and Android applications. For WebUI applications, it should be noted that the log outputs occur at the server. |