Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
visionx:use_log4j [2025/06/23 13:30] admin |
visionx:use_log4j [2025/06/23 13:31] (current) admin |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| This is a very technical article and it's only relevant for developers or experienced users. Usually the integrated log mechanism is good enough, but from a developer point of view it might be helpful to use a different log mechanism. | This is a very technical article and it's only relevant for developers or experienced users. Usually the integrated log mechanism is good enough, but from a developer point of view it might be helpful to use a different log mechanism. | ||
| - | Every application will be created with a **loggerfactory.properties** in the **test** directory. If you keep the file in the test directory, your application won't use it after installation. If you want to use it for the installed application, just move the file to the **src.server** folder. To configure log4j, simply remove the **#** from the first line. It will look like | + | Every application will be created with a **loggerfactory.properties** in the **test** directory. If you keep the file in the test directory, your application won't use customized logging after installation/deployment. If you want to use customized logging for the installed/deployed application, just move the file to the **src.server** folder. To configure log4j, simply remove the **#** from the first line. It will look like |
| <code> | <code> | ||