deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DELTASPIKE-122) producer for logger
Date Mon, 15 Oct 2012 07:30:03 GMT

    [ https://issues.apache.org/jira/browse/DELTASPIKE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476007#comment-13476007
] 

Mark Struberg commented on DELTASPIKE-122:
------------------------------------------

What was the outcome of the discussion? Afair we settled on not implementing this as logging
is hell anyway and we do not like to introduce just another logging framework. Also we would
need to handle Serialisation which is _only_ implementable in a performant way if you know
the underlying logging framework. Imo all this just doesn't make sense from a pure performance
aspect.
                
> producer for logger
> -------------------
>
>                 Key: DELTASPIKE-122
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-122
>             Project: DeltaSpike
>          Issue Type: New Feature
>            Reporter: Romain Manni-Bucau
>            Assignee: Gerhard Petracek
>
> Logger is generally boilerplate code:
> private static final Logger LOGGER  = LoggerFactory.getLogger(Foo.class);
> it could be very nice to get the logger injected by cdi:
> @Inject private Logger logger;
> Then it could be enhanced providing qualifiers for several log implementations (slf4j,
log4j, commons-logging...)
> There is such a feature in weld (weld-clogger) and codi.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message