[
https://issues.apache.org/jira/browse/LOG4J2-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Vent updated LOG4J2-2156:
-----------------------------------
Description:
According to [LOG4J2-462] a LogEvent should never return null for _getLevel()_.
But _org.apache.logging.log4j.core.AbstractLogEvent_ is currently returning
null as level, which will lead to an NPE, if one extends this class to create
an own LogEvent, without overriding the getLevel() method.
Suggestion is to remove _getLevel()_ from the abstract class, to force
developers to decide which level should be returned.
was:
According to [LOG4J2-462] a LogEvent should never return null for _getLevel()_.
But _org.apache.logging.log4j.core.AbstractLogEvent_ is currently returning
null as level, which will lead to an NPE, if one extends this class to create
an own LogEvent, without overriding the getLevel() method.
Suggestion is to remove *getLevel()* from the abstract class, to force
developers to decide which level should be returned.
> AbstractLogEvent should not implement getLevel()
> ------------------------------------------------
>
> Key: LOG4J2-2156
> URL: https://issues.apache.org/jira/browse/LOG4J2-2156
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Reporter: Christian Vent
> Priority: Minor
>
> According to [LOG4J2-462] a LogEvent should never return null for
> _getLevel()_. But _org.apache.logging.log4j.core.AbstractLogEvent_ is
> currently returning null as level, which will lead to an NPE, if one extends
> this class to create an own LogEvent, without overriding the getLevel()
> method.
> Suggestion is to remove _getLevel()_ from the abstract class, to force
> developers to decide which level should be returned.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
