@RqueueListener Generic results not support #59
Replies: 6 comments
|
yes that's a limitation. Would you mind providing a fix if you know? You need to change |
|
no problem. i need to deal with other work recently. u need to wait |
|
Hi, @sonus21 Do the generic results support now? |
|
Hi @chanmratekoko There're some complexity with supporting generic object, in serialisation step we need to track the generic information. GenericMessageConverter is responsible for (de)serialisation. You can provide a new implementation of this class in your application to use. If your generic class has some fixed generic information then it can be addressed easily but as soon as you start adding more generic data it becomes quite messy. This is the reason most of the library does not support deserialisation correctly event spring-data-redis fail on this. Some experimental codes can be seen in this class GenericMessageConverterTest Hope you find a universal working soln. Play with Gson and see if that works for your use case, then you can use Gson in your code for some of the queues. |
|
@sonus21 kafka + spring boot , It's easy to use Multiple projects can be implemented alternately Many rules supporting spring I don't think you should be discouraged, But that's the reality Continuing to maintain this project will waste you a lot of time |
|
@victory-wu not sure if your comment is related to other ticket #47 There're some limitation, give me some more time, I'm working on code to change it to use Redis Stream that's new data structure in Redis. |
Uh oh!
There was an error while loading. Please reload this page.
ERROR:
java.lang.ClassCastException: java.util.LinkedHashMap cannot be cast to com.wzx.server.entity.m.CustomerInfo
analysis:
It does not support generic parsing and is converted to LinkHashMap by default
All reactions