背景:公司项目使用springboot + rabbitMQ 处理订单和推送消息,最开始的时候,producer都是直接convertAndSend的json数据,
consumer也是接收json数据,然后在转化为Bean去处理逻辑。当然,这样虽然没啥大问题,但是感觉很麻烦,后来查阅文档,SpringAMQP可以指定MessageConverter
消息转换器,自动封装Mesage发送,这样就可以直接发送消费对象了,其实说白了,就就是把频繁的json序列化和反序列化的过程,封装到MessageConverter里面去处理而已.
具体不多说,直接上代码:
@Override
protected Message createMessage(Object object, MessageProperties messageProperties) {
//约定,发送消息的除了Bean 就是 String, 不会有其他类型
byte[] bytes = null;
try {
String jsonString = null;
if(object instanceof String){
jsonString=(String) object;
}else {
jsonString = gson.toJson(object);
}
bytes = jsonString.getBytes(CHARSET_NAME);
}
catch (IOException e) {
throw new MessageConversionException(
"Failed to convert Message content", e);
}
messageProperties.setContentType(MessageProperties.CONTENT_TYPE_JSON);
messageProperties.setContentEncoding(CHARSET_NAME);
//设置消息持久化
messageProperties.setDeliveryMode(MessageDeliveryMode.PERSISTENT);
if (bytes != null) {
messageProperties.setContentLength(bytes.length);
}
classMapper.fromClass(object.getClass(),messageProperties);
return new Message(bytes, messageProperties);
}
@Override
public Object fromMessage(Message message)
throws MessageConversionException {
Object content = null;
MessageProperties properties = message.getMessageProperties();
if (properties != null) {
String contentType = properties.getContentType();
if (contentType != null && contentType.contains("json")) {
String encoding = properties.getContentEncoding();
if (encoding == null) {
encoding = CHARSET_NAME;
}
try {
Class<?> targetClass = classMapper.toClass(properties);
content = convertBytesToObject(message.getBody(),
encoding, targetClass);
}
catch (IOException e) {
throw new MessageConversionException(
"Failed to convert Message content", e);
}
}
else {
log.warn("Could not convert incoming message with content-type ["
+ contentType + "]");
}
}
if (content == null) {
content = message.getBody();
}
return content;
}
一般情况下,消息发送者和消费者在不同的项目里面,可能消息实体对应的包名或者类名都不一定完全一样,这样消费者在接收消息的时候,出现找不到类的异常,如下所以:
Caused by: java.lang.ClassNotFoundException: com.demo.Push.Order
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[na:1.8.0_91]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_91]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) ~[na:1.8.0_91]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_91]
当然,如果连名称,包路径都完全一样,则没有上述问题,但是问题是,谁能保证发送端和消费的对象的路径完全一致呢?
没办法,使用了个笨办法,发送端修改如下:
修改自定义的MyClassMapper里面的 fromClass 方法,只穿类的名称
@Override
public void fromClass(Class<?> clazz, MessageProperties properties) {
properties.setHeader(DEFAULT_TYPE_CLASS, clazz.getSimpleName());
}
然后在消费端,自定义的MyClassMapper中配置需要消费的所有对象的map,如下所示:
public class MyClassMapper implements ClassMapper {
private static final String DEFAULT_TYPE_CLASS="__TypeId__";
public static Map<String, Class<?>> mqObjectMap=new HashMap<String, Class<?>>();
static{
mqObjectMap.put(PushMsg.class.getSimpleName(),PushMsg.class);
}
@Override
public Class<?> toClass(MessageProperties properties) {
Object obj = properties.getHeaders().get(DEFAULT_TYPE_CLASS);
if(null != obj){
return mqObjectMap.get(obj.toString());
}
return null;
}
@Override
public void fromClass(Class<?> clazz, MessageProperties properties) {
properties.setHeader(DEFAULT_TYPE_CLASS, clazz.getSimpleName());
}
}
测试,是可以的,但是 总体修改下来,感觉还不如最初直接用json 处理方便,也是蛋疼
折腾了半天,最后我还是选择保证类名报名路径完全一致,不改了
参考博客:https://blog.csdn.net/shengsummer/article/details/79082225