The 0-8 and 0-9-1 AMQP specifications do not define an Message class or interface. Instead, when performing an
operation such as basicPublish the content is passed as a byte-array argument and additional properties are passed in
as separate arguments. Spring AMQP defines a Message class as part of a more general AMQP domain model
representation. The purpose of the Message class is to simply encapsulate the body and properties within a single
instance so that the rest of the AMQP API can in turn be simpler.
Mark Pollack, Mark Fisher, Oleg Zhurakousky, Dave Syer, Gary Russell, Alex Panchenko, Artem Bilan
public static void addAllowedListPatterns(String... patterns)
Add patterns to the allowed list of permissible package/class name patterns for
deserialization in toString().
The patterns will be applied in order until a match is found.
A class can be fully qualified or a wildcard '*' is allowed at the
beginning or end of the class name.
Examples: com.foo.*, *.MyClass.
By default, only java.util and java.lang classes will be
patterns - the patterns.
public static void setDefaultEncoding(String encoding)