The documentation[1] states that the logging profile filenames located in the GEOSERVER_DATA_DIR/logs folder must match the _LOGGING. expression. But in practice we realized that they must actually end with _LOGGING.xml in order to appear in the settings page. Looking at the source-code we found two references [2][3] to the profile filename checking (although we might be missing more). As it can be seen in the code, one is checking just for the presence of _LOGGING, and the other if the name ends with _LOGGING.xml.
So at this point we are not sure if it’s a documentation or code bug. Would be happy to open a Jira issue after knowing your opinion on this.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this communication in error, please notify the sender immediately and delete it. If you are not the intended recipient, you are expressly prohibited from reading, copying, distributing, disseminating or, in any other way, using any of the information without the Magnet consent. Please note that Internet e-mail guarantees neither the confidentiality nor the proper receipt of the message sent, so that Magnet shall not be liable for any damages caused. As its integrity cannot be secured on the Internet, the Magnet liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
It is probably a code bug, if you have a logging profile with _LOGGING.properties or _LOGGING.yaml I would like it to be listed. I only wrote a custom xml parser (to modify the geoserver log filename during loading) so the other file formats will need to have an explicit filename.
Apparently the code also deals with _LOGGING.properties files [1], but I didn’t have the chance to test it. Actually, our problem was with XML files. Our logging profiles were named something like ‘xxxx_LOGGING_xxx.xml’. According to the docs it should be a valid filename, but the administration UI ignores it.
Not a critical bug at all, renaming the files to just ‘xxxx_LOGGING.xml’ makes it work, but just wanted to point it out.
22/8/30 20:37(e)an, Jody Garnett igorleak idatzi zuen:
It is probably a code bug, if you have a logging profile with _LOGGING.properties or _LOGGING.yaml I would like it to be listed. I only wrote a custom xml parser (to modify the geoserver log filename during loading) so the other file formats will need to have an explicit filename.
The documentation[1] states that the logging profile filenames located in the GEOSERVER_DATA_DIR/logs folder must match the _LOGGING. expression. But in practice we realized that they must actually end with _LOGGING.xml in order to appear in the settings page. Looking at the source-code we found two references [2][3] to the profile filename checking (although we might be missing more). As it can be seen in the code, one is checking just for the presence of _LOGGING, and the other if the name ends with _LOGGING.xml.
So at this point we are not sure if it’s a documentation or code bug. Would be happy to open a Jira issue after knowing your opinion on this.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this communication in error, please notify the sender immediately and delete it. If you are not the intended recipient, you are expressly prohibited from reading, copying, distributing, disseminating or, in any other way, using any of the information without the Magnet consent. Please note that Internet e-mail guarantees neither the confidentiality nor the proper receipt of the message sent, so that Magnet shall not be liable for any damages caused. As its integrity cannot be secured on the Internet, the Magnet liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this communication in error, please notify the sender immediately and delete it. If you are not the intended recipient, you are expressly prohibited from reading, copying, distributing, disseminating or, in any other way, using any of the information without the Magnet consent. Please note that Internet e-mail guarantees neither the confidentiality nor the proper receipt of the message sent, so that Magnet shall not be liable for any damages caused. As its integrity cannot be secured on the Internet, the Magnet liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
