Deprecated API

Contents

• Terminally Deprecated
• Interfaces
• Methods

Terminally Deprecated Elements

Element	Description
org.jboss.logging.Logger.getMessageLogger(Class<T>, String)	Use Logger.getMessageLogger(Lookup,Class,String) instead to avoid errors in modular environments.
org.jboss.logging.Logger.getMessageLogger(Class<T>, String, Locale)	Use Logger.getMessageLogger(Lookup,Class,String,Locale) instead to avoid errors in modular environments.
org.jboss.logging.Messages.getBundle(Class<T>)	Use Messages.getBundle(Lookup,Class) instead to avoid errors in modular environments.
org.jboss.logging.Messages.getBundle(Class<T>, Locale)	Use Messages.getBundle(Lookup,Class,Locale) instead to avoid errors in modular environments.

Deprecated Interfaces

Interface	Description
org.jboss.logging.ParameterConverter	this is not currently used anywhere and no replacement will be created

Deprecated Methods

Method	Description
org.jboss.logging.Logger.debug(Object, Object[])	To log a message with parameters, using Logger.debugv(String, Object...) is recommended.
org.jboss.logging.Logger.debug(Object, Object[], Throwable)	To log a message with parameters, using Logger.debugv(Throwable, String, Object...) is recommended.
org.jboss.logging.Logger.error(Object, Object[])	To log a message with parameters, using Logger.errorv(String, Object...) is recommended.
org.jboss.logging.Logger.error(Object, Object[], Throwable)	To log a message with parameters, using Logger.errorv(Throwable, String, Object...) is recommended.
org.jboss.logging.Logger.fatal(Object, Object[])	To log a message with parameters, using Logger.fatalv(String, Object...) is recommended.
org.jboss.logging.Logger.fatal(Object, Object[], Throwable)	To log a message with parameters, using Logger.fatalv(Throwable, String, Object...) is recommended.
org.jboss.logging.Logger.getMessageLogger(Class<T>, String)	Use Logger.getMessageLogger(Lookup,Class,String) instead to avoid errors in modular environments.
org.jboss.logging.Logger.getMessageLogger(Class<T>, String, Locale)	Use Logger.getMessageLogger(Lookup,Class,String,Locale) instead to avoid errors in modular environments.
org.jboss.logging.Logger.info(Object, Object[])	To log a message with parameters, using Logger.infov(String, Object...) is recommended.
org.jboss.logging.Logger.info(Object, Object[], Throwable)	To log a message with parameters, using Logger.infov(Throwable, String, Object...) is recommended.
org.jboss.logging.Logger.log(Logger.Level, Object, Object[])	To log a message with parameters, using Logger.logv(Level, String, Object...) is recommended.
org.jboss.logging.Logger.log(Logger.Level, Object, Object[], Throwable)	To log a message with parameters, using Logger.logv(Level, Throwable, String, Object...) is recommended.
org.jboss.logging.Logger.trace(Object, Object[])	To log a message with parameters, using Logger.tracev(String, Object...) is recommended.
org.jboss.logging.Logger.trace(Object, Object[], Throwable)	To log a message with parameters, using Logger.tracev(Throwable, String, Object...) is recommended.
org.jboss.logging.Logger.warn(Object, Object[])	To log a message with parameters, using Logger.warnv(String, Object...) is recommended.
org.jboss.logging.Logger.warn(Object, Object[], Throwable)	To log a message with parameters, using Logger.warnv(Throwable, String, Object...) is recommended.
org.jboss.logging.Messages.getBundle(Class<T>)	Use Messages.getBundle(Lookup,Class) instead to avoid errors in modular environments.
org.jboss.logging.Messages.getBundle(Class<T>, Locale)	Use Messages.getBundle(Lookup,Class,Locale) instead to avoid errors in modular environments.