We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
如果能够使得cap4j与CAP的message消息格式保持一致,意味着实现java与dotnet程序间的无缝对接,为异构系统的兼容性提供支持,帮助更多的团队拓展技术栈。
cap4j
CAP
java
dotnet
CAP 项目: https://github.com/dotnetcore/CAP
https://github.com/dotnetcore/CAP/blob/master/src/DotNetCore.CAP/Messages/TransportMessage.cs
https://github.com/dotnetcore/CAP/blob/master/src/DotNetCore.CAP/Messages/Message.cs
可能的解决方案:
option 1. cap4j发送到MQ的消息格式保持与CAP一致 option 2. 分别提供Java、dotnet版本的消息消费端的消息格式转换组件包
The text was updated successfully, but these errors were encountered:
No branches or pull requests
如果能够使得
cap4j
与CAP
的message消息格式保持一致,意味着实现java
与dotnet
程序间的无缝对接,为异构系统的兼容性提供支持,帮助更多的团队拓展技术栈。CAP
项目:https://github.com/dotnetcore/CAP
https://github.com/dotnetcore/CAP/blob/master/src/DotNetCore.CAP/Messages/TransportMessage.cs
https://github.com/dotnetcore/CAP/blob/master/src/DotNetCore.CAP/Messages/Message.cs
可能的解决方案:
option 1.
cap4j
发送到MQ的消息格式保持与CAP
一致option 2. 分别提供Java、dotnet版本的消息消费端的消息格式转换组件包
The text was updated successfully, but these errors were encountered: