-
Terminally Deprecated ElementsElementDescriptionin Openfire 4.4 in favour of
PluginManager.getPluginByName(String)Replaced bySrvRecordReplaced bySrvRecord.prioritize(SrvRecord[])Use java.util.Base64 instead.in favour ofCache.getLock(K). Will be removed in Openfire 5.0.0.Returns an existing
Lockon the specified key or creates a new one if none was found. This operation is thread safe. Successive calls with the same key may or may not return the sameLock. However, different threads asking for the same Lock at the same time will get the same Lock object.The supplied cache may or may not be used depending whether the server is running on cluster mode or not. When not running as part of a cluster then the lock will be unrelated to the cache and will only be visible in this JVM.
Use instead thread-safe implementations provided by Java, such asDateTimeFormatterUse java.util.Base64 instead.Use java.util.Base64 instead.Use java.util.Base64 instead.
-
Deprecated ClassesClassDescriptionReplaced by
SrvRecordOld, pre NIO / MINA code. Should not be used as Netty offers better performance. Currently only in use for server dialback.Old, pre NIO / MINA code. Should not be used as Netty offers better performance. Currently only in use for server dialback.Use java.util.Base64 instead.Use instead thread-safe implementations provided by Java, such asDateTimeFormatter
-
Deprecated FieldsFieldDescriptionnot implemented for Netty as this uses max of 1 message per read instead
-
Deprecated MethodsMethodDescriptionReplaced by
IpUtils.isAddressInAnyOf(String, Set)Prefer using the corresponding factory method, rather than invoking methods on the provider directlyin Openfire 4.4 in favour ofPluginManager.getPluginByName(String)Use FormField#parseFirstValueAsBoolean(String) provided by Tinder version 1.3.1 or newer.Replaced bySrvRecord.prioritize(SrvRecord[])- for test use onlyin favour ofCache.getLock(K). Will be removed in Openfire 5.0.0.Returns an existing
Lockon the specified key or creates a new one if none was found. This operation is thread safe. Successive calls with the same key may or may not return the sameLock. However, different threads asking for the same Lock at the same time will get the same Lock object.The supplied cache may or may not be used depending whether the server is running on cluster mode or not. When not running as part of a cluster then the lock will be unrelated to the cache and will only be visible in this JVM.
Use java.util.Base64 instead.Use java.util.Base64 instead.Use java.util.Base64 instead.
-
Deprecated Constructors
IpUtils.isAddressInAnyOf(String, Set)