Global logging feature, deprecate the logging extension and move its functionality to the core extension

[ppalaga]

Fix #270

[ppalaga]

This is quite a major change. @shumonsharif @famod, would you like to express your opinion, whether this is a good idea?

[ppalaga]

Any chance to review or (n)ack?

[shumonsharif]

Hi @ppalaga Overall, I think it's a great idea, and the PR looks great as well. Please feel free to merge it.

Digging into this, I was left wondering a few things on logging, even though they may not be directly tied to the PR - some docs on the below may help others.

• Can we specify the format for the CXF specific log messages easily?
• Can we change the log levels at runtime (using -D JVM arguments)?

[ppalaga]

Thanks @shumonsharif , those are good ideas, I have filed #1107

[famod]

@ppalaga first off, I finally answered you initial question: #270 (comment)
And of course thanks for addressing this topic!

One question: That quarkus.cxf.logging.enabled-for = clients|services|clients-and-services|none idea didn't make it in the end, right?
So you can only enable/disable logging for clients and services globally, but you can disable/enable for clients or services via two distinct properties or even per client or service, right?

[ppalaga]

One question: That quarkus.cxf.logging.enabled-for = clients|services|clients-and-services|none idea didn't make it in the end, right?

No, because I forgot 😂. I can implement it if you find it useful?

So you can only enable/disable logging for clients and services globally, but you can disable/enable for clients or services via two distinct properties or even per client or service, right?

Yes, with current impl, if you enable logging globally, you can still mute it for individual clients and services by passing quarkus.cxf.[client.myClient|endpoint."/foo"].logging.enabled = false

[ppalaga]

3c0e443: Added quarkus.cxf.logging.enabled-for = clients|services|clients-and-services|none.