New issue
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
Reopen of #962 - ISSUE WITH KAMELET azure-servicebus-source output is message length instead of message #980
Comments
@oscerd |
The message from servicebus is always binary. It's up to you to work with that. |
@oscerd |
Because it was enough to re-open the old ticket, instead of opening a new one. |
One problem would be you need to call the toBytes() on the binaryData. We could do that, in the Kamelet for the moment and with a new Camel release in the component. |
This should be fixed with #983 |
ISSUE WITH KAMELET azure-servicebus-source output is message length instead of message
I had below KameletBinding working with Timer source but with Azure ServiceBus.
I was getting a type conversion error
Caused by: org.apache.camel.NoTypeConversionAvailableException: No type converter available to convert from type: com.azure.core.util.BinaryData to the required type: java.io.InputStream
Hence, I added a JSON Serializer in between
Now the PROBLEM is that instead of capturing data it's capturing length of the message
{"length":54}{"length":54}{"length":54}{"length":54}{"length":54}
How to fix this?
Do I need to configure the azure-servicebus-source Kamelet to make it output String/JSON? Is it reasonable to configure the Kamelet or should I copy and configure that one?
The text was updated successfully, but these errors were encountered: