cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Wulff (JIRA)" <>
Subject [jira] [Commented] (CXF-5010) Add customizable request logging capability to STS
Date Tue, 16 Jul 2013 06:26:48 GMT


Oliver Wulff commented on CXF-5010:

I fully agree with you with respect to the scope of the cxf framework because CXF is bundled
in all sorts of combinations with other frameworks. But I don't understand the issue with
the dependency on the spring framework on a service component as we don't add spring dependency
to all applications using the CXF framework but only to the STS service.
The CXF STS service uses spring anyway (sts-war and sts-core). Can you elaborate what the
issue is?
Can't we find a solution for 2.7.6 as I'm just waiting to get this new feature promoted to
production with the release version?

> Add customizable request logging capability to STS
> --------------------------------------------------
>                 Key: CXF-5010
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>          Components: STS
>            Reporter: Oliver Wulff
>            Assignee: Oliver Wulff
>             Fix For: 2.7.6, 3.0.0
> As discussed in [1] add an customizable logging mechanism in the STS thus you can log
every successful or failed request. The log message should be customizable what kind of context
information should be logged like:
> - issue/validate/...
> - principal
> - appliesto
> - token type
> - exception
> - ...
> The Spring eventing mechanism provides an easy way in adding event handling. The event
provides all context information like TokenProviderParameters or TokenValidatorParameters,
etc for processing.
> A default implementation is provided which uses the CXF Logging API to log the information
to a file (or what is configured).
> If you want to change the logging you can just configure a spring bean which implements
the Spring ApplicationListener.
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message