-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message Logging uses Deprecated API and can be refactored to the new Logging-Feature #72
Comments
Is this somehow related to #47 ? |
marcopaga
changed the title
Property 'soap.messages.logging' has no effect
Property 'soap.messages.logging' has no effect in client mode
Feb 21, 2020
We were not using the client that is provided by the starter, so the automatic setup doesn't work. We couldn't set credentials for the client so we needed to go a bit offroad. I'll create a ticket for client credentials and link it here. |
marcopaga
changed the title
Property 'soap.messages.logging' has no effect in client mode
Message Logging uses Deprecated API and can be refactored to the new Logging-Feature
Feb 25, 2020
marcopaga
added a commit
that referenced
this issue
Oct 23, 2020
…ase keep in mind that this commit is a WIP one ;) I would like to discuss the idea behind logging and the current implementation to find a sweet spot for this starter. My way is to move some implicit couplings to the ELK Stack out of this codebase. The CXF Logging Feature (https://cxf.apache.org/docs/message-logging.html) can handle some of our needs. This change would cause us to talk about the configuration properties. E.g. * I can control logging of WebService endpoints using the standard spring boot mechanisms. * (Re)move explicit creation of ELK Tags and use the one created by the Feature?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The property
soap.messages.logging=true
has no effect on the logging output.The text was updated successfully, but these errors were encountered: